This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC Plug-in Framework ready to port
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Diego Novillo <dnovillo at google dot com>
- Cc: Taras Glek <tglek at mozilla dot com>, Sean Callanan <spyffe at cs dot sunysb dot edu>, Basile STARYNKEVITCH <basile at starynkevitch dot net>, Grigori Fursin <grigori dot fursin at inria dot fr>, Le-Chun Wu <lcwu at google dot com>, Brendon Costa <bcosta at avdat dot com dot au>, Emmanuel Fleury <fleury at labri dot fr>, gcc at gcc dot gnu dot org
- Date: Sun, 1 Feb 2009 19:34:20 +0000 (UTC)
- Subject: Re: GCC Plug-in Framework ready to port
- References: <m3iqnwwqrl.fsf@google.com> <EFC35277-A978-4B6E-9F06-DC56C1409B99@cs.sunysb.edu> <b798aad50901310511o3884804fs2f5392e509ab14df@mail.gmail.com> <4984D585.3010306@mozilla.com> <b798aad50902011018v6edb792fg7ada13bdec7fd55@mail.gmail.com> <Pine.LNX.4.64.0902011846180.21239@digraph.polyomino.org.uk> <b798aad50902011126i34ac0e71k8dc40bb223f66c75@mail.gmail.com>
On Sun, 1 Feb 2009, Diego Novillo wrote:
> > As for installation directories, I've already noted that plugins should be
> > installed under libsubdir or libexecsubdir since they will depend on both
> > the target and version of GCC.
>
> Agreed. We'll also need some convention for the API header files.
Those will also depend on both target and version; somewhere under
libsubdir also probably works for them (the configure macros provided by
GCC for plugin writers can deal with finding them for users). They'll
also need to include some generated files (for example, plugins are bound
to need to know the configured HOST_WIDE_INT, which depends on
NEED_64BIT_HOST_WIDE_INT, even if anyone manages to separate cleanly those
cases that are about the host from those relating more to the target).
--
Joseph S. Myers
joseph@codesourcery.com