Ian Lance Taylor wrote: > 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). > > Thanks for the input.
The one-liner shell script is a very good option. The GCC_PLUGINS env var method is very similar to what i use currently, though would require GCC to look for such an environment variable. It would have basically the same affect as searching a directory for such a list of plugins, but is more configurable and another way of achieving "automatically loaded" plugins. I think i will follow up the script idea. Thanks, Brendon.
