This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [plugin] Directory for plugins distributed with gcc
- From: Olatunji Ruwase <tjruwase at google dot com>
- To: Diego Novillo <dnovillo at google dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 15 Jul 2009 11:50:48 -0700
- Subject: Re: [plugin] Directory for plugins distributed with gcc
- References: <fe7fd8170907151130j35ac3348kb447e7e1d273d9af@mail.gmail.com> <b798aad50907151143v5abe42daj897861ed5591724c@mail.gmail.com>
Sorry that I wasn't very specific with my question. I m currently
wrapping up the conversion of
mudflap into a plugin. Most of the required patches have being
approved and committed, so I was
thinking ahead as to where the the plugin code will reside.
Thanks for the information and the link
tunji
On Wed, Jul 15, 2009 at 11:43 AM, Diego Novillo<dnovillo@google.com> wrote:
> [ Moved to gcc@ ]
>
> On Wed, Jul 15, 2009 at 14:30, Olatunji Ruwase<tjruwase@google.com> wrote:
>
>> ?Has any decision being made on how plugins will be distributed with
>> future releases. Is there going to be a plugins directory ?.
>> ?Thanks
>
> We may want to produce some plugins that are useful for GCC
> development and distribute them with the compiler, but in general I
> don't think we should get in the habit of incorporating 3rd party
> plugins in GCC. ?This would be detrimental to one of the useful
> properties of plugins (i.e., less code we need to maintain).
>
> I set up a landing page where projects can register their plugins
> (http://gcc.gnu.org/wiki/plugins). ?My suggestion is to use that page
> as the central plugins directory, with the assumption that we (GCC)
> are not the maintainers of those packages. ?We simply provide a link
> to them.
>
>
> Diego.
>