Defining a common plugin machinery

Ian Lance Taylor
Fri Sep 19 13:59:00 GMT 2008

Brendon Costa <> 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).


More information about the Gcc mailing list