pkg-config doesn't depend on glib. It comes with it's own copy of glib-1.2 but you shouldn't have to worry about that.
In the native win32 build, it does depend on glib (which I believe is what Bob is using). But I agree, it's not important.
Then, glib doesn't actually depend on pkg-config. configure only checks for it's presense since we think that pkg-config should be installed when glib is installed. This is just a convenience check to catch problems early. pkg-config is not used at all during the glib build process.
If, and when, libiconv and/or gettext provide a .pc file, I would like glib's configure to use pkg-config to find them. It would make my life easier :-)
Whatever, pkg-config is just a build tool. It doesn't need to be present on the target platform and it should not be a problem to install pkg-config on the build host (especially since it comes packaged with all distributions).
Indeed. It runs on systems where autoconf can't run (eg., win32 without cgywin installed) and, contrary to Tristan's views, I find it invaluable when cross-compiling.
This has nothing to do with the development of glib.
Cheers,
Ali. _______________________________________________ gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
