pkgconfig 0.14

Howdy folks -

This is slightly off topic, but I was hoping that some of you might be able
to help me out.  I've been attempting to get the gimp to build successfully
under Windows, and it's been a slow trail with a rather steep learning
curve,  but I'm getting there.  However, it's obvious that this would be a
much smoother journey if I had a more complete understanding of how all of
the build related tools work, especially from the user-installer side of
things.  So, I decided to tackle what I anticipated would be a much smaller
and simpler task before getting back to building the gimp.  I decided to try
to build and install the latest stable version of pkg-config, which of
course is one of the tools that is used to help build and install the gimp.

I downloaded, unzipped, and untarred pkgconfig-0.14.0 .  I read through the
rather meager install and readme files.  The install looked like it ought to
be pretty simple, with only one seemingly minor issue:  pkg-config includes
and is normally built with glib 1.2.x on unix derivatives, but on windows
you have to use glib 2.0.x.  I looked in configure and the various other
build related files, and saw lots of conditional checking based on the host
and build environment, including specific checks related to the MinGW/mSys
environment that I'm using.  So, I thought that everything would be ok.
WRONG!

I cd into the top level directory and run ./configure .  Everything seems ok
at that point.  Then I attempt to run make.  It quickly blows up as it
starts to build the included glib-1.2.8 subdirectory.  That it blows up is
no surprise, since glib-1.2.8 is not compatible with Windows to my
understanding.  However, what I don't understand is why it ever started
building that subdirectory in the first place???  Seems like it should have
detected that I'm on a Win32 based host, and therefore bypassed any attempt
to build glib-1.2.8, using my previously installed glib-2.0 libraries
instead.

Now unlike the gimp, all of the pkg-config source modules are right there in
 the top level directory.  So, there is no opportunity to simply cd down
into some other subdirectory and run make on that.  You have to run make in
the top level directory here.  So, what am I missing???  How do I tell
either configure or make in some manner that I don't want to recursively
make the glib-1.2.8 subdirectory?  I know that I could completely hack up
the make file and eliminate any recursive stuff.  But surely there must be
an easier way to force the glib directory to be bypassed!

Is this a bug or oversight in the pkg-config configure and/or make files, or
am I just ignorant of some simple and commonly used option that controls
this behavior.

Thanks in advance.

s/KAM