On 4/26/2011 22:20, Jon wrote: >>> I've read the >>> https://sourceforge.net/mailarchive/message.php?msg_id=25062006 thread and >>> would like to know the latest mingw-w64 recommendations for using >>> LIBRARY_PATH. While I would like to be able to use LIBRARY_PATH as I do >>> with other MinGW-based toolchains, is there another env var or setting >>> other than -L I should be using? >>> >> >> Looks like it does ignore it, so avoid using LIBRARY_PATH. For >> autotool'ed buildsystems, use LDFLAGS=-L.../lib and >> CPPFLAGS=-I.../include to point to additional search locations. > > Thanks, using LDFLAGS and CFLAGS seems to work best for my specific setup. > > Is LIBRARY_PATH ignored in my case because i686-w64-mingw32-gcc.exe thinks > it's cross-compiling between i686-w64-mingw32 and i686-pc-mingw32? My > understanding is LIBRARY_PATH is ignored when cross-compiling but not other > cases, and I want to make sure I get this issue before moving on. >
No, the compiler doesn't work that way. The compiler you are using IS BUILT as a cross compiler, so it IS a cross compiler. Using autotools has nothing to do with it.
0xED74C077.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
