* Alon Bar-Lev wrote on Thu, Jan 07, 2010 at 09:07:46AM CET: > > For some strange reason this workaround does not work in Windows when > > creating a DLL. > > > > I get: > > --- > > /bin/sh ../../../../libtool --tag=CC --mode=link > > x86_64-w64-mingw32-gcc -g -O2 -pedantic -Wall -Wextra -module > > -shared -avoid-version -no-undefined -export-symbols x.exports -o x.la > > -rpath /tmp/xxx/lib x.lo ../../../../src/lib/core/libcore.la -lws2_32 > > > > *** Warning: This system can not link to static lib archive > > ../../../../src/lib/core/libcore.la. > > *** 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. > > *** But as you try to build a module library, libtool will still create > > *** a static module, that should work as long as the dlopening application > > *** is linked with the -dlopen flag to resolve symbols at runtime. > > --- > > > > If I modify libtool: > > if test "$deplibs_check_method" != pass_all; then > > To: > > if false && test "$deplibs_check_method" != pass_all; then > > > > It works...
> Any idea how to workaround/solve this on windows host? I'm not sure I understand correctly. libtool prints a warning, but should not fail. Is the result usable? If not, then the build should end with an error in a later link: can you post it and its output? Thanks, Ralf _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
