This is the mail archive of the gcc-patches@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: default plugin directory?


On Thu, Jun 18, 2009 at 09:30, Basile
STARYNKEVITCH<basile@starynkevitch.net> wrote:

> Concretely, I am suggesting that some users would pass just
> Â-fplugin=treehydra
> instead of the full path
> Â-fplugin=/usr/lib/gcc/x86_64-linux-gnu/4.5.1/plugins/treehydra.so

I'm not sure I like this idea.  One can always declare a variable
containing the path to the plugins inside a Makefile or build script.

However, if we are going to do this.  How about make it a switch like -B or -L?

$ gcc -fplugin-path=<dir> -fplugin=plugin1 -fplugin=plugin2

Instead of having one magic directory.


Diego.


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