From: Michael G. <mg...@te...> - 2005-12-14 18:47:47
|
> It's autotooled so libtool handles all the library stuff. The point is=20 > adding mingw support to the current structure and not creating an entire= =20 > new build system just for one platform. Ok. > automake & co generates the makefile, so there's few additions on my=20 > part. But here is what is finally executed: >=20 > /bin/sh ../libtool --mode=3Dlink i386-mingw32msvc-gcc -D_GNU_SOURCE=20 > -I/home/ossman/polypaudio -I/usr/local/cross-w32//include=20 > -I/usr/local/cross-w32//include=20 > -DDLSEARCHPATH=3D\"/usr/local/cross-w32//lib/polypaudio-0.8\"=20 > -DDEFAULT_CONFIG_DIR=3D\"/usr/local/cross-w32//etc/polypaudio\"=20 > -DPOLYPAUDIO_BINARY=3D\"/usr/local/cross-w32//bin/polypaudio\"=20 > '-DDEBUG_TRAP=3D__asm__("int $3")' -g -O2 -pipe -W -Wall -pedantic=20 > -std=3Dgnu9x -Wno-unused-parameter -no-undefined -o=20 > libpolyp-simple-0.8.la -rpath /usr/local/cross-w32//lib -version-info=20 > 0:0:0 libpolyp_simple_0.8_la-polyplib-simple.lo libpolyp-0.8.la=20 > libpolyp-mainloop-0.8.la -lm >=20 > Which gives me: >=20 > *** Warning: linker path does not have real file for library -lm. > *** I have the capability to make that library automatically link in when > *** you link to this library. But I can only do this if you have a > *** shared version of the library, which you do not appear to have > *** because I did check the linker path looking for a file starting > *** with libm and none of the candidates passed a file format test > *** using a file magic. Last file checked:=20 > /usr/local/cross-w32/lib/gcc-lib/i386-mingw32msvc/3.2/../../../../i386-mi= ngw32msvc/lib//libm.a > *** The inter-library dependencies that have been dropped here will be > *** automatically added whenever a program is linked with this library > *** or is declared to -dlopen it. I'm not sure wether it is of any importance but why are there these doubled '//' in your paths ? And could it be that this prevents libtool from finding your libm.a which I presume can be found under /usr/local/cross-w32/i386-mingw32msvc/lib/libm.a Just guessing. > If I bastardise libtool and remove the check for the above, it links=20 > fine. I haven't gotten to the point of linking the library to something=20 > functional yet so I don't know if it produces a correct dll. If the above guesswork is correct then it should work fine. Best, Michael =2D-=20 Vote against SPAM - see http://www.politik-digital.de/spam/ Michael Gerdau email: mg...@te... GPG-keys available on request or at public keyserver |