Menu
▾
▴
mingw-users
|
From: Stefano S. <ste...@po...> - 2010-06-15 12:55:09
|
Hi all, I need to install pkg-config, and I'm reading: http://www.mingw.org/wiki/FAQ - How do I get pkg-config installed? The entry states: |The difficulty in getting pkg-config installed is due its circular |depency on glib. To install pkg-config, you should first install the |GTK-runtime, the installer is found at |http://sourceforge.net/project/showfiles.php?group_id=121075. The |pkg-config binary can be obtained from |http://www.gtk.org/download-windows.html. Place pkg-config.exe in your |MinGW bin directory. The first link: http://sourceforge.net/project/showfiles.php?group_id=121075 points to the Gimp+GTK download page (no GTK runtime installer alone). Question: do I really need to install Gimp in order to get pkg-config installed? The page pointed by the second link: http://www.gtk.org/download-windows.html lists both Glib/GTK packages and the pkg-config package, so it is somehow confusing (which version of pkg-config, GTK, GLib have to be installed?). Finally I wonder why there is no pkg-config already pre-compiled, I suppose that having that depending on Gimp/GTK/GTK+/GLib/GodKnowsWhat etc. doesn't help it. Regards. |
|
From: Stefano S. <ste...@po...> - 2010-06-15 13:12:24
|
On date Tuesday 2010-06-15 14:54:27 +0200, Stefano Sabatini wrote: > Hi all, > > I need to install pkg-config, and I'm reading: > http://www.mingw.org/wiki/FAQ - How do I get pkg-config installed? > > The entry states: > |The difficulty in getting pkg-config installed is due its circular > |depency on glib. To install pkg-config, you should first install the > |GTK-runtime, the installer is found at > |http://sourceforge.net/project/showfiles.php?group_id=121075. The > |pkg-config binary can be obtained from > |http://www.gtk.org/download-windows.html. Place pkg-config.exe in your > |MinGW bin directory. > > The first link: > http://sourceforge.net/project/showfiles.php?group_id=121075 > > points to the Gimp+GTK download page (no GTK runtime installer > alone). > > Question: do I really need to install Gimp in order to get pkg-config > installed? > > The page pointed by the second link: > http://www.gtk.org/download-windows.html > > lists both Glib/GTK packages and the pkg-config package, so it is > somehow confusing (which version of pkg-config, GTK, GLib have to be > installed?). > > Finally I wonder why there is no pkg-config already pre-compiled, I > suppose that having that depending on Gimp/GTK/GTK+/GLib/GodKnowsWhat > etc. doesn't help it. Anyway from the GTK docs pkg-config depends on glib, I suppose it should safe just install the glib bin and pkg-config bin packages. BTW should I install them in the MinGW root or in the MSYS one? Does it make any difference? TIA, regards. |
|
From: Tor L. <tm...@ik...> - 2010-06-15 13:22:44
|
> BTW should I install them in the MinGW root or in the MSYS one? Does > it make any difference? Personally, I would say in neither, and advice to keep stuff from each separate larger 3rd-party source in a separate tree. But this is mostly a matter of taste, and how good you are at keeping track of what you have where. --tml |
|
From: LRN <lr...@gm...> - 2010-06-15 13:27:48
|
On 15.06.2010 17:22, Tor Lillqvist wrote: >> BTW should I install them in the MinGW root or in the MSYS one? Does >> it make any difference? >> > Personally, I would say in neither, and advice to keep stuff from each > separate larger 3rd-party source in a separate tree. But this is > mostly a matter of taste, and how good you are at keeping track of > what you have where. > > --tml > Keep MinGW packages in /mingw, MSys packages in /, and everything else in /local/ |
|
From: Stefano S. <ste...@po...> - 2010-06-15 14:03:30
|
On date Tuesday 2010-06-15 17:27:33 +0400, LRN wrote: > On 15.06.2010 17:22, Tor Lillqvist wrote: > >> BTW should I install them in the MinGW root or in the MSYS one? Does > >> it make any difference? > >> > > Personally, I would say in neither, and advice to keep stuff from each > > separate larger 3rd-party source in a separate tree. But this is > > mostly a matter of taste, and how good you are at keeping track of > > what you have where. > > > > --tml > > > Keep MinGW packages in /mingw, MSys packages in /, and everything else > in /local/ I read many guides since now, the paths usually suggested or implicitely used are (most of the times, and there are contradictions): MINGW_DIR=<DRIVE>:\MinGW MSYS_DIR =<DRIVE>:\MSYS\<MSYS_VERSION> This works for me, not that I'm saying it's the best practice though. Regards. |
|
From: Earnie <ea...@us...> - 2010-06-15 17:05:26
|
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. -- Earnie -- http://www.for-my-kids.com |
|
From: LRN <lr...@gm...> - 2010-06-15 17:18:44
|
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. |
|
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 |
|
From: Earnie <ea...@us...> - 2010-06-16 14:17:09
|
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. For those who have experience in overcoming the obstacles it may be fine. For those who do not, then we subscribe to the what I've stated. If the paths are not as we advertise and you have an issue with finding a header or a library then you will be instructed to reinstall the package per the preferred method. -- Earnie -- http://www.for-my-kids.com |
|
From: Charles W. <cwi...@us...> - 2010-06-17 01:15:23
|
On 6/15/2010 1:18 PM, LRN wrote:
> 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 /
As Earnie said downthread, there are two "problems" with this:
(1) in the old days people tended to mix "msys" apps -- and, more
problematically, libraries -- and "mingw" ones in the /local/ tree. If
you tell your compiler (either msys-gcc or mingw-gcc) to "look" in
/local/{include,lib} for stuff, then you get a mixture, and that's bad.
(2) By default, neither msys-gcc nor mingw-gcc "look" in /usr/local or
/local/. So, you have to manually tell it to do so; it doesn't work
"Out Of The Box".
An experienced user can easily work around or avoid these problems, and
create an kind of installation tree they desire. But our official
recommendations are meant for novice users -- experienced ones don't
need recommendations anyway.
--
Chuck
|
|
From: Tor L. <tm...@ik...> - 2010-06-15 13:14:18
|
> The entry states: > |The difficulty in getting pkg-config installed is due its circular > |depency on glib. I think "install" here should be interpreted as meaning "install by building from source code". > Finally I wonder why there is no pkg-config already pre-compiled, There is, linked to from the second page you mentioned, http://www.gtk.org/download-windows.html . Points to http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/pkg-config_0.23-3_win32.zip . (Of course, the gtk.org or ftp.gnome.org sites are not part of MinGW, so if you think that MinGW should be a complete "distribution" and provide through the mingw.org site open source software you want built for Windows, they are not "good enough".) Anyway, if you just download the above and try to run the pkg-config.exe program, you will notice that it requires libglib-2.0-0.dll, which is provided in a glib package. Any reasonably recent 2.x version would work, for instance that in http://ftp.gnome.org/pub/gnome/binaries/win32/glib/2.24/glib_2.24.0-2_win32.zip . pkg-config has no other 3rd-party dependencies. --tml |
|
From: Stefano S. <ste...@po...> - 2010-06-15 13:57:57
|
On date Tuesday 2010-06-15 16:13:51 +0300, Tor Lillqvist wrote: > > The entry states: > > |The difficulty in getting pkg-config installed is due its circular > > |depency on glib. > > I think "install" here should be interpreted as meaning "install by > building from source code". > > > Finally I wonder why there is no pkg-config already pre-compiled, > > There is, linked to from the second page you mentioned, > http://www.gtk.org/download-windows.html . Points to > http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/pkg-config_0.23-3_win32.zip > . > > (Of course, the gtk.org or ftp.gnome.org sites are not part of MinGW, > so if you think that MinGW should be a complete "distribution" and > provide through the mingw.org site open source software you want built > for Windows, they are not "good enough".) As far as I understood it MinGW/MSYS are here to provide a way for running configure && make for a source package in Windows, since pkg-config is required by many configure scripts, having a glib and pkg-config in MSYS would be nice. That why I'd just have to add them to my setup-mingw-files.txt file and I had them automatically installed with no further steps required. > Anyway, if you just download the above and try to run the > pkg-config.exe program, you will notice that it requires > libglib-2.0-0.dll, which is provided in a glib package. Any reasonably > recent 2.x version would work, for instance that in > http://ftp.gnome.org/pub/gnome/binaries/win32/glib/2.24/glib_2.24.0-2_win32.zip > . > > pkg-config has no other 3rd-party dependencies. Well I can confirm that I just installed glib 2.24.0 and pkg-config 0.23-3 from the page: http://www.gtk.org/download-windows.html and pkg-config seems to work fine. Thanks, regards. |
|
From: Vincent T. <vt...@un...> - 2010-06-15 15:44:37
|
On Tue, 15 Jun 2010, Stefano Sabatini wrote: > As far as I understood it MinGW/MSYS are here to provide a way for > running configure && make for a source package in Windows, since > pkg-config is required by many configure scripts, having a glib and > pkg-config in MSYS would be nice. you also usually need pkg.m4, which is in the dev package of pkg-config (gtk+ download page) Vincent Torri > > That why I'd just have to add them to my setup-mingw-files.txt file > and I had them automatically installed with no further steps required. > >> Anyway, if you just download the above and try to run the >> pkg-config.exe program, you will notice that it requires >> libglib-2.0-0.dll, which is provided in a glib package. Any reasonably >> recent 2.x version would work, for instance that in >> http://ftp.gnome.org/pub/gnome/binaries/win32/glib/2.24/glib_2.24.0-2_win32.zip >> . >> >> pkg-config has no other 3rd-party dependencies. > > Well I can confirm that I just installed glib 2.24.0 and pkg-config > 0.23-3 from the page: > http://www.gtk.org/download-windows.html > > and pkg-config seems to work fine. > > Thanks, regards. > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. Disregard for the list etiquette may cause your account to be moderated. > > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > > |
