PKG_CHECK_MODULES output

[Daniel Macks]

On Sun, Oct 22, 2006 at 10:41:25PM +0100, Alberto Sim?es wrote:
> On 10/22/06, Tollef Fog Heen <tfheen at err.no> wrote:
> >* "Alberto Sim?es"
> >
> >| I use pkg-config for some time, but noticed something today that I
> >| think it wasnt before. Anyway, I am using
> >|   PKG_CHECK_MODULES([GLIB], [glib-2.0])
> >| and the output in the configure script is:
> >|   checking for GLIB...
> >|
> >| It shouldn't be:
> >|   checking for glib-2.0 ?
> >
> >Arguably, yes.  The problem with that is when people start embedding
> >newlines and it quickly looks fairly ugly with:
> >
> >checking for         gtk+-2.0                                >= 2.6
> >        pygtk-2.0                               >= 2.6
> >        pygobject-2.0                   >= 2.6
> >        gnome-python-2.0                >= 2.10
> >        gnome-desktop-2.0               >= 2.10...
> >
> >Yes, it could be collapsed to something like:
> >
> >checking for gtk+-2.0 >= 2.6 pygtk-2.0 >= 2.6 pygobject-2.0 >= 2.6
> >gnome-python-2.0 >= 2.10 gnome-desktop-2.0 >= 2.10
> >
> >but it's not that much more readable.
> 
> I see your point. I would prefer this last option compared to the
> current one, but probably is just me. I'll give a quick look to the
> macro and check if I have any idea for a patch.

We need to have "GLIB" displayed so that if it fails, one knows that
it's GLIB_CFLAGS and GLIB_LDFLAGS that need to be overloaded from the
environment. IMO, *if* the check succeeds, do people really care that
much which specific requirements were checked? OTOH, if the check
fails, then one really *does* need that info in order to figure out
what needs to be installed.

dan

-- 
Daniel Macks
dmacks at netspace.org
http://www.netspace.org/~dmacks