Re: magick/GraphicsMagick.pc.in in 1.1.2

On Thu, Jul 22, 2004 at 02:02:43PM -0500, Bob Friesenhahn wrote:
> On Thu, 22 Jul 2004, Albert Chin wrote:
> 
> >Why do you have the following in magick/GraphicsMagick.pc.in:
> > Libs: @MAGICK_API_LDFLAGS@ @MAGICK_API_LIBS@
> > Cflags: @MAGICK_API_CPPFLAGS@
> >
> >The standard would be:
> > Libs: -L${libdir} -lGraphicsMagick
> > Cflags: -I${includedir}
> 
> Wouldn't that constrain the dependent application so that it must be 
> installed using the same prefix as GraphicsMagick?  Or does pkg-config 
> expand ${libdir} and ${includedir} automatically while reporting them?

${libdir} should be taken literally. In GM's case, it should probably be
${libdir}@MagickLibSubdir@.

And yes, ${libdir} and ${includedir} get expanded because earlier in
the .pc file you have:
  libdir=@libdir@
  includedir=@includedir@

> There are some flags added via @MAGICK_API_CPPFLAGS@ which may be 
> important.  For example, flags are added for multithread support.

Ok. Then maybe:
  Cflags: -I${includedir}@blah@ @GM_CPPFLAGS@

-- 
albert chin ([email protected])


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click