[MacOS10.4.10, wxMac2.8, gcc 4.0.1] Resuscitating an old thread: "Automating" the use of wx-config

David Goldsmith David.L.Goldsmith at noaa.gov
Fri Sep 14 10:49:14 PDT 2007


Riccardo Cohen wrote:
> it seems that the resulting config used gcc instead of g++, I couldn't 
> say why
Thanks Riccardo.  Well, my /usr/bin/gcc is a link to gcc-4.0.1, not 
g++-4.0.1.  I can change it manually (I can't see in the gcc_select man 
page how to change it to anything other than a version of gcc), but if 
wx-config should be calling g++ instead of gcc, I'd rather fix that, but 
how?

DG
>
> David Goldsmith wrote:
>> Matt Connolly wrote:
>>> Actually, to fully make use of the "wx-config" command you can do:
>>>
>>> For compiling:
>>>
>>> `wx-config --cc` `wx-config --cppflags` <my_flags> <source_files> ...
>>>
>>> For linking:
>>>
>>> `wx-config --ld` `wx-config --libs` <my_flags> <object_files> ...
>>>
>>> -matt
>> Hi, folks!  Haven't used this method in a while and I don't remember 
>> if I had the same problem last time I did.  The above implies to me 
>> that `wx-config --cc` `wx-config --cppflags` <my_flags> 
>> <source_files> will stop after compiling, i.e., not proceed on to 
>> linking, but that is not what I'm observing:
>>
>> dg$ `wx-config --cc` `wx-config --cppflags` -Wno-deprecated -I 
>> ../../../Source/CompCore *cpp ../../../Source/CompCore/*.cpp
>> /usr/bin/ld: Undefined symbols:
>> __Unwind_Resume
>> wxThread::TestDestroy()
>> wxThread::~wxThread()
>> typeinfo for wxThread
>> vtable for __cxxabiv1::__si_class_type_info
>> operator delete(void*)
>> operator new(unsigned long)
>> ___gxx_personality_v0
>> wxStringBase::npos
>> wxStringBase::InitWith(char const*, unsigned long, unsigned long)
>> wxMessageBox(wxString const&, wxString const&, long, wxWindow*, int, 
>> int)
>> vtable for __cxxabiv1::__class_type_info
>> ___cxa_begin_catch
>> ___cxa_end_catch
>> operator new[](unsigned long)
>> _dgbtrf_
>> _dgbtrs_
>> collect2: ld returned 1 exit status
>>
>> i.e., `wx-config --cc` `wx-config --cppflags` <my_flags> 
>> <source_files> is proceeding on to linking - am I just 
>> misinterpreting "For compiling:"?
>>
>> Second Q: why am I getting the (wx) linking errors?
>>
>> DG
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: wx-users-unsubscribe at lists.wxwidgets.org
>> For additional commands, e-mail: wx-users-help at lists.wxwidgets.org
>>
>>
>

-- 
ERD/ORR/NOS/NOAA <http://response.restoration.noaa.gov/emergencyresponse/>




More information about the wx-users mailing list