Build problems (SVN HEAD / wxMac)
in [wxWindows]
|
From: Jim on 22 Apr 2008 10:10 Hi, I'm trying to build wxWidgets head on Leopard, and I'm getting the linker errors: Undefined symbols: "_iconv_close", referenced from: wxMBConv_iconv::~wxMBConv_iconv()in monodll_strconv.o wxMBConv_iconv::~wxMBConv_iconv()in monodll_strconv.o wxMBConv_iconv::~wxMBConv_iconv()in monodll_strconv.o wxMBConv_iconv::~wxMBConv_iconv()in monodll_strconv.o "_iconv_open", referenced from: wxMBConv_iconv::wxMBConv_iconv(char const*)in monodll_strconv.o wxMBConv_iconv::wxMBConv_iconv(char const*)in monodll_strconv.o wxMBConv_iconv::wxMBConv_iconv(char const*)in monodll_strconv.o wxMBConv_iconv::wxMBConv_iconv(char const*)in monodll_strconv.o My configure looks like: .../configure --prefix=/opt/wx29x --with-mac --with-opengl --enable- geometry --enable-graphics-ctx --enable-sound --with-sdl --enable- mediactrl --enable-display --enable-monolithic --enable-unicode --with- libjpeg=builtin --with-libpng=builtin --with-libtiff=builtin --with- zlib=builtin What could I be doing wrong? (or what dependancy would give me _iconv_close?)
From: Thomas Hauk on 22 Apr 2008 11:20 On Apr 22, 2008, at 7:10 AM, Jim wrote: > What could I be doing wrong? (or what dependancy would give me > _iconv_close?) I use Xcode to build on Mac, so I'm not sure about using the command line, but I know you have to link against libiconv. T -- "It's a very sobering feeling to be up in space and realise that one's safety factor was determined by the lowest bidder on a government contract.'' -- Alan Shepherd
From: Stefan Csomor on 22 Apr 2008 11:58 Hi if you are fine compiling for Leopard only then things are ok when linking against libconv, but if you want your code to run on Tiger as well, you should avoid it, since the version on leopard is newer and you'll get linkage errors when starting the app under Tiger. I wrote about that a few months ago and IIRC we've added the necesary configure line so -with-iconv=no should work for the command line Best, Stefan On 22.04.08 17:20, "Thomas Hauk" <thauk(a)novuscom.net> wrote: > On Apr 22, 2008, at 7:10 AM, Jim wrote: >> What could I be doing wrong? (or what dependancy would give me >> _iconv_close?) > > > I use Xcode to build on Mac, so I'm not sure about using the command > line, but I know you have to link against libiconv. > > T > > -- > "It's a very sobering feeling to be up in space and realise that one's > safety factor was determined by the lowest bidder on a government > contract.'' > -- Alan Shepherd > > _______________________________________________ > wx-users mailing list > wx-users(a)lists.wxwidgets.org > http://lists.wxwidgets.org/mailman/listinfo/wx-users -- Advanced Concepts AG Software-Engineering Heldweg 10 CH-8475 Ossingen Switzerland phone:+41 52 245 0 245 fax:+41 52 245 0 246 http://www.advanced.ch mailto:csomor(a)advanced.ch
From: Thomas Hauk on 22 Apr 2008 17:41 On Apr 22, 2008, at 8:58 AM, Stefan Csomor wrote: > if you are fine compiling for Leopard only then things are ok when > linking > against libconv, but if you want your code to run on Tiger as well, > you > should avoid it, since the version on leopard is newer and you'll get > linkage errors when starting the app under Tiger. I have an Xcode project that compiles against the 10.4 SDK, with wx 2.8.7, and my client has not had any problems launching the application under 10.4. Can you elaborate more? Also, can you define exactly what should be done to get a project to compile, if not link against libiconv? T -- "Take it to the bridge!" -- James Brown
From: Stefan Csomor on 23 Apr 2008 10:48
Hi On 22.04.08 23:41, "Thomas Hauk" <thauk(a)novuscom.net> wrote: > I have an Xcode project that compiles against the 10.4 SDK, with wx > 2.8.7, and my client has not had any problems launching the > application under 10.4. > > Can you elaborate more? > > Also, can you define exactly what should be done to get a project to > compile, if not link against libiconv? if you compile against 10.4.SDK then there is not problem, since the libiconv there is upwards compatible to 10.5 if you use HEAD against 10.5.SDK then there is no problem for xcode builds because in include/mac/config_xcode.h I've undefined HAVE_ICONV if you want to build wx configure based against a 10.5.SDK and want to use the resulting binary on 10.4 then you must add a -with-iconv=no to configure if you really want to build 2.8 xcode against 10.5.SDK and want to use the resulting binary on 10.4 then you must modify include/mac/carbon/config_xcode.h (different path!) and change #define HAVE_ICONV 1 to /* #undef HAVE_ICONV */ I hope this has cleared things up ... Best, Stefan |