summaryrefslogtreecommitdiff
path: root/README.win32
diff options
context:
space:
mode:
authorLRN <lrn1986@gmail.com>2012-05-18 05:34:07 -0700
committerDan Nicholson <dbn.lists@gmail.com>2012-05-18 09:14:08 -0700
commita80fbc52004feb6a7d84de87dde809c9ed5d66cd (patch)
treeb31e0e8be70a0b159b53da785e719ece79c9dd76 /README.win32
parentd415d9171390bab1f1601641cc0053ab98c1fdd8 (diff)
downloadpkg-config-a80fbc52004feb6a7d84de87dde809c9ed5d66cd.tar.gz
Fix win32 README
A simple documentation fix (reflecting the fact that pkg-config is not being built against glib-1.2 anymore).
Diffstat (limited to 'README.win32')
-rw-r--r--README.win3212
1 files changed, 0 insertions, 12 deletions
diff --git a/README.win32 b/README.win32
index 04ea456..fb84e8f 100644
--- a/README.win32
+++ b/README.win32
@@ -37,16 +37,4 @@ site. This works as long as the .pc file uses the variable name
"prefix" for its installation prefix. At least GLib, ATK, Pango and
GTK does this.
-On Unix, pkg-config is built using its own copy of GLib 1.2.8. On
-Windows, we use the normal GLib available for Windows (2.0.x). Yes,
-this does introduce a kind of circular dependency. But, that can be
-worked around. The circular dependency only appears if one uses the
-configure mechanism to build GLib. GLib's configure script checks for
-pkg-config. pkg-config depends on GLib. Thus, starting from scratch,
-with no GLib and no pkg-config, using configure, there would indeed be
-a Catch-22 situation. However, GLib can be built just fine using the
-manually written makefiles for mingw or MSVC. And if somebody does
-want to build GLib on Win32 using configure, she can first install a
-prebuilt pkgconfig.
-
--Tor Lillqvist <tml@iki.fi>