This is the mail archive of the
mailing list for the GCC project.
Re: default plugin directory?
- From: Diego Novillo <dnovillo at google dot com>
- To: Basile STARYNKEVITCH <basile at starynkevitch dot net>
- Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 19 Jun 2009 07:48:24 -0400
- Subject: Re: default plugin directory?
- References: <4A3A4161.firstname.lastname@example.org>
On Thu, Jun 18, 2009 at 09:30, Basile
> Concretely, I am suggesting that some users would pass just
> instead of the full path
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.