On Sun, 13 Mar 2011 14:27:24 +0100, Colomban wrote:
On Sun, 13 Mar 2011 21:32:48 +1100, Lex wrote:
We could maybe add a little wrapper script into the scripts/ directory which sets a bunch of compiler options we like, for convenience.
Having scripts like these is non-standard so it would have to be *well* documented. I still personally prefer in the build so long as
Ok. But if it's in the build system, it should be optionally and disabled by default, at least.
Ok by me. (So long as how to enable it is obvious somewhere, unlike most other configure options, I'm still not sure how to generate plugins for non-standard prefixes using autofools :-)
Why not, easy enough. However, I'm not completely sure the info in HACKING or whatever would be visible enough for every new (and current! ) developer to see it, but we might start this way and see if it is OK.
I agree it might get forgotten in HACKING...
Something like ./configure --enable-extra-c-warnings (or shorter if you prefer ^^)
...so this sounds good to me. Maybe that option could also display a hint to check HACKING for more information about flags.
Regards, Enrico