This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Finding gcc plugin headers

From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
To: Brad Hards <bradh at frogmouth dot net>
Cc: gcc at gcc dot gnu dot org
Date: Sat, 09 May 2009 16:37:32 +0100
Subject: Re: Finding gcc plugin headers
References: <200905081803.11273.bradh@frogmouth.net> <38a0d8450905080440o15d699e2yb1fb50b87ef42b3f@mail.gmail.com> <4A042787.9070208@gmail.com> <200905091758.49825.bradh@frogmouth.net>

Brad Hards wrote:
> On Friday 08 May 2009 10:37:27 pm Dave Korn wrote:
>>   Instead of pkg-config, the tradition for GCC is to use one of the
>> driver's default switches.  Does
>>
>> gcc -print-file-name=plugin/include/<whatever>.h
>>
>> work for you?
> For those who'd like to use this with cmake, I wrote up the results of my work 
> in a blog entry:
> http://www.kdedevelopers.org/node/3952
> 

  Ah, I was about to mention the gotcha about getting the argument returned
verbatim when it can't find it but I see you already dealt with it yourself.
I noticed one bit that looked like a typo:

# we don't have this path - it needs some suffix

  ITYM 'prefix' here, no?

    cheers,
      DaveK

Follow-Ups:
- Re: Finding gcc plugin headers
  - From: Brad Hards

References:
- Finding gcc plugin headers
  - From: Brad Hards
- Re: Finding gcc plugin headers
  - From: Rafael Espindola
- Re: Finding gcc plugin headers
  - From: Dave Korn
- Re: Finding gcc plugin headers
  - From: Brad Hards

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]