RE: [bug #13383] missing path in openbsd build

[Nicola Pero]

Checking for pkg-config (and using it if available) to determine the png 
include path 
seems like a good idea; I imagine you'd want to do the check directly inside 
gnustep-gui's
configure though. ;-)

I mean, I imagine we'd end up writing code which is something like

AC_CHECK_PROG(HAVE_PKG_CONFIG, pkg-config, yes)

if test "x$HAVE_PKG_CONFIG" = "xyes"
then
  PKG_CHECK_MODULES(...)
else
  <manual check without pkg-config ?>
fi

Anyway, checking for pkg-config seems to be the easiest thing to do since it's a
single autoconf macro. :-)  So we wouldn't gain much by saving that information
somewhere inside gnustep-make [actually we might be making things more 
complicated as
then we need to import the information into the configure.ac file!]. ;-)

Thanks

-----Original Message-----
From: David Ayers <INVALID.NOREPLY@gnu.org>
Sent: Sun, March 18, 2007 2:00 pm
To: David Ayers <ayers@fsfe.org>, Nicola Pero 
<nicola.pero@meta-innovation.com>, Sebastian Reitenbach <buzzdee@web.de>, 
bug-gnustep@gnu.org
Subject: [bug #13383] missing path in openbsd build


Follow-up Comment #6, bug #13383 (project gnustep):

Interesting... not what I would have expected, but it seems that this will be
'fixed' in future versions of OpenBSD proper.

Thank you for checking!

I still think we should be using pkg-config /if/ it is available to determine
the build flags.

Nicola, what do you think?
And if you agree, do you agree that a "global" check for pkg-config should go
into -make?
And should the result be cached somewhere to be included by -gui's
configure?


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?13383>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/