|
From: Vincent T. <vt...@un...> - 2010-06-15 22:18:54
|
On Tue, 15 Jun 2010, LRN wrote: > On 15.06.2010 21:05, Earnie wrote: >> LRN wrote: >> >>> Keep MinGW packages in /mingw, MSys packages in /, and everything else >>> in /local/ >>> >>> >> Actually, the advertised and supported method for MinGW is to put any >> "native" application (those not requiring the MSYS DLL) in /mingw and >> MSYS applications in /. If you put "everything else" in /local then you >> are on your own for the support especially where something isn't found >> because it isn't in /mingw. >> >> > Why? To me it makes perfect sense that package-originated files are in > /mingw and in /, while everything i build from the source (or what i > download in a pre-built form - basically something installed with make > install DESTDIR=/somewhere and archived) goes into /local/ . This way i > never have to mess with any files in /mingw or / > A fine point is that pkg-config should be in /local/bin in this case, > because otherwise it won't be able to locate *.pc files in > /local/lib/pkgconfig without explicit instructions. But since GTK (which > is the way i'm usually getting pkg-config - AFAIK there is no special > pkg-config MinGW package either) is not a MinGW package, it goes into > /local/ for me, so this is not a problem. i think that he just want to say that CPPFLAGS, LDFLAGS, LIBS, PATH, PKG_CONFIG_PATH etc... env variables must also be set so that everything is correctly detected. Btw, I agree with you. I usually put everything else in /usr/local and set the needed env var in /etc/profile file. I even installed some specific libraries in other directories. Once you know what to do, there is no problem at all. Vincent Torri |