2009/5/27 Basile STARYNKEVITCH <bas...@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.
