Date: Sat, 7 Apr 2001 08:47:39 +0200 From: Stijn Hoop <stijn@win.tue.nl> To: Marc van Woerkom <van.woerkom@netcologne.de> Cc: freebsd-gnats-submit@freebsd.org, ports@freebsd.org Subject: Re: %20ports/26104:%20PORT%20UPDATE%3A%20add%20%24%7BFREETYPE%5FCONFIG%7D%20support%20for%20graphics%2Fgd Message-ID: <20010407084739.A58824@pcwin002.win.tue.nl> In-Reply-To: <200104062034.f36KY3u08063@oranje.my.domain>; from van.woerkom@netcologne.de on Fri, Apr 06, 2001 at 10:34:03PM %2B0200 References: <200104062034.f36KY3u08063@oranje.my.domain>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 06, 2001 at 10:34:03PM +0200, Marc van Woerkom wrote:
> Hi,
>
> I ran into the same trap over here (latest XF4).
>
> The suggested fix is not general enough:
>
> > --- /usr/ports/graphics/gd/Makefile Sun Feb 25 05:30:46 2001
> > +++ gd/Makefile Mon Mar 26 11:05:28 2001
> > @@ -20,6 +20,8 @@
> > jpeg.9:${PORTSDIR}/graphics/jpeg \
> > freetype.6:${PORTSDIR}/print/freetype2
> >
> >+FREETYPE_CONFIG?= ${LOCALBASE}/bin/freetype-config
> >
>
> I suppose that "freetype-config" utility comes with the stand-alone
> freetype2 library from ports/print/freetype2,
> but XFree86 4.0.3, which is also a source for libfreetype.6,
> does not come with a freetype-config utility and if it would,
> it would probably put its into ${X11BASE}/bin.
Yes, the various XFree86-4-* ports _do_ install freetype-config in
${X11BASE}/bin. However, without this not-so-correct fix, I can't
even tell the port that I do have freetype-config. With it, I can
at least use it, although I have to think and do a
make FREETYPE_CONFIG=${X11BASE}/bin/freetype-config install
So therefore I still think it's worthwhile enough to be committed.
> I can think of these solutions:
>
> 1. have ports/graphics/gd/Makefile find out the full path where
> libfreetype.6 is installed, use the prefix of this
> path (/usr/X11.., /usr/local.., ..) to look for the includes
> as well
That would be OK.
> 2. add a freetype-config script to XF4 port
> (and change ${LOCALBASE}/bin/freetype-config into plain freetype-config,
> hoping the right one is in PATH)
This is the best solution IMHO.
> RFC:
>
> This "foo-config" script technique seems to be popular with the
> Linux/GTK bunch.
>
> I once asked Havoc about it and he responded:
>
> http://sources.redhat.com/ml/inti/2000-q4/msg00014.html
>
>
> Thus the generalisation is a generic "pkg-config" command
> with a repository of options in "${SOME_PREFIX}/lib/pkg-config/*.pc".
>
> We could write a BSD "pkg_config" config command which retrieves
> such information from
>
> /var/db/<lib-name>/+CONFIG
>
> where +CONFIG holds the gcc options to link against the
> library.
Hmm, interesting thought. Maybe +CONFIG could also record the various
WITH_ and WITHOUT_ options used to install the port? Then one would
be able to depend on a port WITH_GNOME or WITHOUT_GNOME support...
--Stijn
--
Nostalgia ain't what it used to be.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010407084739.A58824>