Re: [Jsbsimcommander-devel] can't read input file :(

[Lee D. <le...@ea...>]

Matthew Gong wrote:
> Hi, Lee
>   It seems that you may need update the cvs files.
>
> it should have been changed from
>   alpha_max = wxString::Format("%g", data->alphaclmax);
> to
>   alpha_max = wxString::Format(wxT("%g"), data->alphaclmax);
>
> In wxWidgets,
> wxT("abc") micro means "abc" in ansi build, but L"abc" in unicode build;
> and wxChar means char in ansi build, but w_char in unicode build.
>
>
> Matt
>
> 在 2007-09-25二的 12:11 -0400，Lee Duke写道：
>   
>> I tried jsbsimcommander on Fedora Core 6. I did
>>         ./configure
>>         make
>> I got the following errors:
>>         [snip]
>>         AeroDynamics_Diag.cpp:145: error: no matching function for
>>         call to ‘wxString::Format(const char [3], const double&)’
>>         /usr/include/wx-2.6/wx/string.h:1085: note: candidates are:
>>         static wxString wxString::Format(const wxChar*, ...)
>>         AeroDynamics_Diag.cpp:146: error: no matching function for
>>         call to ‘wxString::Format(const char [3], const double&)’
>>         /usr/include/wx-2.6/wx/string.h:1085: note: candidates are:
>>         static wxString wxString::Format(const wxChar*, ...)
>>         AeroDynamics_Diag.cpp:151: error: no matching function for
>>         call to ‘wxString::Format(const char [3], const double&)’
>>         /usr/include/wx-2.6/wx/string.h:1085: note: candidates are:
>>         static wxString wxString::Format(const wxChar*, ...)
>>         AeroDynamics_Diag.cpp:152: error: no matching function for
>>         call to ‘wxString::Format(const char [3], const double&)’
>>         /usr/include/wx-2.6/wx/string.h:1085: note: candidates are:
>>         static wxString wxString::Format(const wxChar*, ...)
>>         make[2]: *** [AeroDynamics_Diag.o] Error 1
>>         make[2]: Leaving directory
>>         `/home/duke/Simulation/JSBSimCommander-0.1.1/src/gui'
>>         make[1]: *** [all-recursive] Error 1
>>         make[1]: Leaving directory
>>         `/home/duke/Simulation/JSBSimCommander-0.1.1/src'
>>         make: *** [all-recursive] Error 1
>>         [duke@localhost JSBSimCommander-0.1.1]$ 
>>         
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2005.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________ Jsbsimcommander-devel mailing list Jsb...@li... https://lists.sourceforge.net/lists/listinfo/jsbsimcommander-devel
>>     
>
>
>   
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Jsbsimcommander-devel mailing list
> Jsb...@li...
> https://lists.sourceforge.net/lists/listinfo/jsbsimcommander-devel
>   
Okay. I updated my files from the cvs repository.

Now, besides about two billion warnings, I get:

    [snip]
    sensor.cpp:199: error: ambiguous overload for ‘operator<<’ in
    ‘((wxTextOutputStream*)((wxTextOutputStream*)((wxTextOutputStream*)stream)->wxTextOutputStream::operator<<(((const
    wxString&)((const wxString*)(&
    Pre)))))->wxTextOutputStream::operator<<(((const wchar_t*)"
    \000\000\000
    \000\000\000<\000\000\000m\000\000\000a\000\000\000x\000\000\000>\000\000\000\000\000\000")))->wxTextOutputStream::operator<<(((Sensor*)this)->Sensor::min)
    << "</max>"’
    [snip]
    sensor.cpp:247: error: no match for ‘operator=’ in
    ‘((Sensor*)this)->Sensor::quant_property =
    JSBSim::Element::GetAttributeValue(std::string)(std::basic_string<char,
    std::char_traits<char>, std::allocator<char> >(((const
    char*)"name"), ((const std::allocator<char>&)((const
    std::allocator<char>*)(& std::allocator<char>())))))’


I wouldn't normally complain about the warning, but in this case they 
make it very difficult to spot the errors.

Lee