public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
To: Basile STARYNKEVITCH <basile@starynkevitch.net>
Cc: GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: plugins & howto & generators
Date: Wed, 27 May 2009 17:58:00 -0000	[thread overview]
Message-ID: <6c33472e0905270930p2239b6f8u91916f4beb934804@mail.gmail.com> (raw)
In-Reply-To: <4A1D5CAB.1080004@starynkevitch.net>

2009/5/27 Basile STARYNKEVITCH <basile@starynkevitch.net>:
> Hello All,
>
> We now have plugins and they are somehow documented.
> http://gcc.gnu.org/onlinedocs/gccint/Plugins.html
>
> Perhaps we might document how to build a plugin? (Or should we not bother?)

In particular, in the wiki, it is better to err on the side of too
much documentation. If someone can be bothered, then it is probably
useful.

> Should we tell them (the other users using the future gcc-4.5-dev Debian
> package) in our documentation how to build a plugin (I mean what are the
> actual commands to run, what kind of Makefile for them, what are the
> required CFLAGS or -I... path, etc..), or should that be left to e.g. linux
> distribution packagers?

A complete tutorial on how to create and build a generic plugin is
perhaps more suited for the wiki than for the internals documentation.
Plugin authors should describe how to build their plugins, which may
require special flags or commands. Popular plugins will probably be
built (and packaged) by distributions.

Cheers,

Manuel.

  reply	other threads:[~2009-05-27 16:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 17:31 Basile STARYNKEVITCH
2009-05-27 17:58 ` Manuel López-Ibáñez [this message]
2009-05-28  4:53   ` Dave Korn
2009-05-28 23:04   ` Joseph S. Myers

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=6c33472e0905270930p2239b6f8u91916f4beb934804@mail.gmail.com \
    --to=lopezibanez@gmail.com \
    --cc=basile@starynkevitch.net \
    --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).