On Wed, Nov 12, 2014 at 02:29:13PM +0100, Jakub Jelinek wrote: > On Wed, Nov 12, 2014 at 02:20:22PM +0100, Basile Starynkevitch wrote: > > Most plugin don't need any configure, because they are installed in > > a version specific directory (like /usr/lib/gcc/x86_64-linux-gnu/4.9/plugin > > for example). I don't think it is wise to require plugin to be > > autoconf-configurable. Their Makefile simply uses > > $(shell gcc -print-file-name=plugin), there is no need to complex > > autoconf machinery. > > If you use $(shell gcc -print-file-name=plugin), there is no point > to include plugin-version.h, just use __GNUC__/__GNUC_MINOR__ ?
I could compile a plugin (notably for a GCC cross-compiler) with a GCC version different of the GCC targetting the plugin. I could also compile a plugin with Clang or some other non-GCC compiler. In both cases plugin-version.h is needed with its GCCPLUGIN_VERSION. Cheers. -- Basile Starynkevitch http://starynkevitch.net/Basile/