This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [plugins] [patch] Initial implementation of GCC plugin support
- From: Basile STARYNKEVITCH <basile at starynkevitch dot net>
- To: Gerald Pfeifer <gerald at pfeifer dot com>
- Cc: Benjamin Smedberg <benjamin at smedbergs dot us>, "Joseph S. Myers" <joseph at codesourcery dot com>, Le-Chun Wu <lcwu at google dot com>, gcc-patches at gcc dot gnu dot org, Diego Novillo <dnovillo at google dot com>, Taras Glek <tglek at mozilla dot com>, Grigori Fursin <grigori dot fursin at inria dot fr>, Zbigniew Chamski <zbigniew dot chamski at gmail dot com>, Sean Callanan <spyffe at cs dot sunysb dot edu>, Cupertino Miranda <cupertinomiranda at gmail dot com>
- Date: Fri, 27 Feb 2009 11:36:42 +0100
- Subject: Re: [plugins] [patch] Initial implementation of GCC plugin support
- References: <82091ad70902201351y79d58552nf90b2359d8b40e0a@mail.gmail.com> <499F6AC3.4060807@starynkevitch.net> <Pine.LNX.4.64.0902210251530.21964@digraph.polyomino.org.uk> <49A3042E.9050004@smedbergs.us> <Pine.LNX.4.64.0902232129460.6792@digraph.polyomino.org.uk> <49A31AAE.6080406@smedbergs.us> <alpine.LSU.1.99.0902271123150.9031@acrux.dbai.tuwien.ac.at>
Gerald Pfeifer wrote:
On Mon, 23 Feb 2009, Benjamin Smedberg wrote:
Building the plugin requires having the GCC sources, not just the plugin
sources. GCC sources don't normally come with distros, so you have to go
through fairly complicated hoops to get the GCC sources which match the
binaries installed on your system.
All distros I am aware of provide the very GCC sources they use to build
their flavor of GCC, generally in easily accessible a manner. (This is the
most straightforward way for them to honor the requirements of the GPL.)
And I would expect future distributions to provide a package for GCC, eg
gcc-4.6 and another package to develop plugin for it, eg gcc-4.6-dev.
This is what is already happenning for other plugin-aware software. For
example, the zsh shell is packaged as zsh for the compiled software and
zsh-dev for the package providing the include and script files needed to
compile plugins for the zsh shell.
Probably the impact for GCC plugin machinery is that:
* we should aim at being able to compile GCC plugins without the GCC
source tree (so obviously having installed required header files elsewhere)
* we should define where the header files (etc... including scripts,
...) required for plugin compilation should go - probably in $(libexec)/...
* we should have isolated makefile targets to install these header
files, and every other stuff (shell scripts, ...) required to compile
GCC plugins
Regards.
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***