-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yes, the gnu libiconv for instance will leave in the *.la file the directory in which the library will be installed and that will create a problem because libtool will not find it there.
Cheers F. Richard W.M. Jones wrote: > I'm a bit confused by what the mistake is .. The *.la files we are > generating now seem to have correct paths inside them. Can you point > to an example where there is a problem? > >> I think that the reason is basically the w32api and mingwrt package >> where make install does not honour DESTDIR setting. Find attached two >> patches that will make that DESTDIR to be respected. >> >> Also, I sent a proposed (IMHO better) mingw32 macros files. Note that >> the CLASSPATH variable is not useful for you people if you don't >> distribute the mingw32-gcc-java cross-compiler that I personally use for >> building of some java bindings of my private libraries. But the >> _mingw32_make and _mingw32_makeinstall macros could be considered I >> guess. I even make the mingw32-make symlink because several non-libtool >> applications cross-compile much better using mingw32-make which sets all >> the needed env variables. > > Rich. > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAklKJEIACgkQu9a1imXPdA/2iwCfQ/VPPbHM2TBkWlFFfZmTNoJi wjEAnRYEnQnpuA1h/w6MnWl/3GfaFBJf =PeAI -----END PGP SIGNATURE----- _______________________________________________ fedora-mingw mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/fedora-mingw
