[Gc] bdw-gc.pc: Cflags: -I${includedir}/pc ?

Boehm, Hans hans.boehm at hp.com
Fri Aug 24 15:42:31 PDT 2007

I probably made the change that caused gc.h to no longer be installed in
$(prefix)/include.  But this was not intentional.  I'm also not a
pkg-config expert or an expert on the conventions here.  Thus I'm very
open to suggestions/patches.


> -----Original Message-----
> From: gc-bounces at napali.hpl.hp.com 
> [mailto:gc-bounces at napali.hpl.hp.com] On Behalf Of Petter Urkedal
> Sent: Thursday, August 23, 2007 12:59 PM
> To: Rex Dieter
> Cc: gc at napali.hpl.hp.com
> Subject: Re: [Gc] bdw-gc.pc: Cflags: -I${includedir}/pc ?
> On 2007-08-23, Rex Dieter wrote:
> > Now, I don't care either way, I just would like to know that the 
> > official/prefered method for apps to use gc's header files.  Is 
> > #include <gc.h> (and using -I/usr/include/gc) or #include<gc/gc.h> 
> > expected/prefered usage?
> I am not to decide the official usage, but I agree it would 
> be good to settle the question.  (I used to test for both 
> gc.h and gc/gc.h in my configure-script before dropping <7.0.)
> Ways to smooth things out would be:
>   * Re-add the installation of ${includedir}/gc.h which includes
>     <gc/gc.h>, assuming this is the only header people 
> include without a
>     directory prefix.
>   * Add another pkg-config file, like bdw-gc-import.pc, with
>     -I${includedir}/gc.  (However, I think projects which 
> include <gc.h>
>     does not yet use pkg-config, or they would have discovered the
>     issue, so this does not completely eliminate the need to port the
>     code.)
> _______________________________________________
> Gc mailing list
> Gc at linux.hpl.hp.com
> https://www.hpl.hp.com/hosted/linux/mail-archives/gc/

More information about the Gc mailing list