From: Olatunji Ruwase <tjruwase@google.com>
To: Diego Novillo <dnovillo@google.com>
Cc: gcc@gcc.gnu.org
Subject: Re: [plugin] Directory for plugins distributed with gcc
Date: Wed, 15 Jul 2009 18:51:00 -0000 [thread overview]
Message-ID: <fe7fd8170907151150g134348c1k5c2ef1a053c57cd2@mail.gmail.com> (raw)
In-Reply-To: <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.
>
next prev parent reply other threads:[~2009-07-15 18:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fe7fd8170907151130j35ac3348kb447e7e1d273d9af@mail.gmail.com>
2009-07-15 18:43 ` Diego Novillo
2009-07-15 18:51 ` Olatunji Ruwase [this message]
2009-07-15 19:14 ` Diego Novillo
2009-07-15 19:36 ` Joseph S. Myers
2009-07-15 20:43 ` Paolo Bonzini
2009-07-15 20:53 ` Joseph S. Myers
2009-07-15 21:16 ` Basile STARYNKEVITCH
2009-07-15 21:43 ` Paolo Bonzini
2009-07-16 13:09 ` Rafael Espindola
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe7fd8170907151150g134348c1k5c2ef1a053c57cd2@mail.gmail.com \
--to=tjruwase@google.com \
--cc=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).