Re: linux to windows cross compile af a dll
On Tue, 2010-08-24 at 18:53 +0200, Ralf Wildenhues wrote: > Which ./libtool --version is your package using? With 2.2.10, > no hacks should be necessary. > > If 2.2.10 is still not working right, please post the output of > the failing 'libtool --mode=link' command, with --debug added as > first argument after libtool. Thank you. j...@panoramix:~$ libtool --version ltmain.sh (GNU libtool) 2.2.6b I will try with 2.2.10.1 from Debian experimental. -- Groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 web: www.askesis.nl signature.asc Description: This is a digitally signed message part ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: linux to windows cross compile af a dll
On Tue, 2010-08-24 at 18:53 +0200, Ralf Wildenhues wrote: > If 2.2.10 is still not working right, please post the output of > the failing 'libtool --mode=link' command, with --debug added as > first argument after libtool. Thank you. I am sorry to say but it fails. Attached the output from the command as requested. BTW: I am not linking with import libraries but to dll's, which afaik should work? -- Groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 web: www.askesis.nl debug.txt.tar.bz2 Description: application/bzip-compressed-tar signature.asc Description: This is a digitally signed message part ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: linux to windows cross compile af a dll
Based on the debug output I changed the names of the Boost dll's from boost_xxx.dll to libboost_xxx.dll and the warning went away. I was under the impression that the search order for libraries was: libxxx.dll.a xxx.dll.a libxxx.a libxxx.dll xxx.dll Apparently it is not so. This trick did NOT work for the static boost_regex-mt. I tried it with prefixing lib, and with .a and .lib as extension. Any ideas anyone? TIA -- Groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 web: www.askesis.nl ___ http://lists.gnu.org/mailman/listinfo/libtool
Libtool 2.2.10 Linux -> windows cross compile bug?
(this is actually a follow-up on the "linux to windows cross compile af a dll") Hi, I am trying to use libtool to do a cross compile on Linux (Debian Sqeeze AMD64) to Windows, using the gcc-mingw32 4.4.4-0.1+b1, mingw32-binutils 2.20-0.1 and libtool 2.2.10. According to http://sourceware.org/binutils/docs/ld/WIN32.html I should be able to link directly to a Windows dll using -lxxx. If I try that libtool complains that it cannot find the library. The libraries are actually there and are named xxx.dll. If I rename the the file to libxxx.dll than libtool finds the library. Is this a bug or am I missing something? TIA -- Groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 web: www.askesis.nl signature.asc Description: This is a digitally signed message part ___ http://lists.gnu.org/mailman/listinfo/libtool
libtool 2.2.10: What is the correct library naming convention
Hi, I have asked this question before, but I got no answer. If I asked it the wrong or impolite way: sorry and please forgive me. What should the file name be of a dll on Windows to let dlltool find it? According to http://sourceware.org/binutils/docs/ld/WIN32.html: For instance, when ld is called with the argument `-lxxx' it will attempt to find, in the first directory of its search path, libxxx.dll.a xxx.dll.a libxxx.a xxx.lib cygxxx.dll (*) libxxx.dll xxx.dll But it appears that libtool insists that is *must* be called libxxx.dll or otherwise the library is not found. Which is rather annoying because several other packages do not use the lib prefix. TIA, -- Groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 web: www.askesis.nl ___ http://lists.gnu.org/mailman/listinfo/libtool
