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: Defining a common plugin machinery

From: Ian Lance Taylor <iant at google dot com>
To: Brendon Costa <bcosta at avdat dot com dot au>
Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, Diego Novillo <dnovillo at google dot com>, gcc at gcc dot gnu dot org, Basile STARYNKEVITCH <basile at starynkevitch dot net>, Sean Callanan <spyffe at cs dot sunysb dot edu>
Date: Thu, 18 Sep 2008 22:38:48 -0700
Subject: Re: Defining a common plugin machinery
References: <48CF93F7.8010901@google.com> <48D2F56B.7060708@avdat.com.au> <Pine.LNX.4.64.0809190107250.2308@digraph.polyomino.org.uk> <48D30EAC.2080704@avdat.com.au>

Brendon Costa <bcosta@avdat.com.au> writes:

> I have control over my project: foo, however i do not have control over
> project blah. The problem is with badly defined build system that do NOT
> allow a user to pass flags they want to to the compiler. This will
> likely result in having to edit the build system code for project blah
> just to build with the necessary compiler flags to include use the plugin.

Write a one-line shell script to use as your compiler (that's what I
would do), or define an environment variable which tells gcc which
plugins to load (e.g., GCC_PLUGINS=/a/file:/another/file).

Ian

Follow-Ups:
- Re: Defining a common plugin machinery
  - From: Brendon Costa

References:
- Defining a common plugin machinery
  - From: Diego Novillo
- Re: Defining a common plugin machinery
  - From: Brendon Costa
- Re: Defining a common plugin machinery
  - From: Joseph S. Myers
- Re: Defining a common plugin machinery
  - From: Brendon Costa

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