On 11/9/2012 00:08, Earnie Boyd wrote: > On Thu, Nov 8, 2012 at 10:03 AM, JonY wrote: >> On 11/8/2012 22:49, Václav Šmilauer wrote: >>> Greetings to experienced Mingw64-ers, >>> >>> I am currently compiling several 3rd-party libraries which I need for my >>> code. Among those are glib, VTK, Qt and perhaps several others. I have >>> the (32bit) MSYS installed, which provides standard directories like >>> /usr/lib, /usr/include, ... >>> >> >> These should not be present, if they are, it is likely it is ONLY for >> MSYS development, which you are not clearly doing, so please move them >> away for safety. >> > > I wouldn't be removing them. There might be some binary dependency on > these, one that comes to mind is perl. >
I forgot about those. >>> When configuring libs, I use --prefix=/c/MinGW64 to not to install them >>> into the 32bit MSYS tree, but I fear that I will have comflicts between >>> 32bit/64bit headers, as the 32bit ones are in the default search path. >>> Secondly, it is a bit tedious to install everything to non-default >>> paths. Is there some solution to this I am overseeing? >>> >> >> Use proper CPPFLAGS and LDFLAGS instead, there is no easy way to deal >> with this. > > If you have your mingw-w64 distribution in c:/MinGW64 then a > --prefix=c:/MinGW64 is appropriate. Otherwise adjust it to point to > your installed location for mingw-w64 GCC. > There isn't an include directory specifically for win32 and another for win64. Installing to the same area will clash as OP predicted.
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
