[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Mingw-cross-env-list] Xerces library problem

From: tek
Subject: [Mingw-cross-env-list] Xerces library problem
Date: Sun, 11 Jul 2010 10:47:46 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv: Gecko/20100619 Icedove/3.0.5

Hi everybody,

I'm in the process of cross-compiling a project using Xerces (under Debian). I did:

$ make xerces

Seems to work, but:

$ ls -l usr/i686-pc-mingw32/lib/libxerces*

-rw-r--r-- 1 tek tek    8 Jul 11 04:11 usr/i686-pc-mingw32/lib/libxerces-c.a
-rwxr-xr-x 1 tek tek 1528 Jul 11 04:11 usr/i686-pc-mingw32/lib/libxerces-c.la

Note the size fields. So, it did not work. Checking logs for xerces build, I noticed these lines of interest:

libtool: link: warning: undefined symbols not allowed in i686-pc-mingw32 shared libraries
libtool: link: i686-pc-mingw32-ar cru .libs/libxerces-c.a
libtool: link: i686-pc-mingw32-ranlib .libs/libxerces-c.a

Searching on the web led me to the assumption that -no-undefined (or --no-undefined) should be given to the linker options when building Xerces may resolve the issue. The fact is... I don't really know how in the context of mingw-cross-env. I could hack a bit for this... but TBH, that's not why I decided to mail here.

I just wonder: is something broken in mingw-cross-env with Xerces or did I miss something? My project also makes intensive use of SDL without problems (well, at least no error reported about it either in mingw-cross-env and my project link time) and OpenGL with minor problems (it mostly has to do with GL shader calls, I'll deal with it in time). But obviously, object files using Xerces lead to undefined references.

My second question is: do you think I should use the Debian package mingw32 instead of mingw-cross-env? Are there some drawbacks (besides the fact I would have to deal manually with a few builds)?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]