On 06-06-2008 10:06:19 +0200, Stefan Manegold wrote:
2) "users production distribution" Ready-to-use for users with all (save) perfoamce benefits, but no (default) need to debug the code line by line (let's face it: which *user* does understand out code in details?). This is (a) the source tarball(s) with defaults --disable-strict --disable-assert --disable-debug --enable-optimize (I don't consider --enable-optimize a "hack" but a well-tested setting for know compiles and scenarios, and hence want users to benefit from it) and (b) the binary packages compiled with the same defaults.
This is where we disagree. a) we should standardise, and not be another project that annoyingly thinks they know better than the very well thought of defaults b) with agressive optimisations, such as --enable-optimize, it is IMO quite wrong to distribute the resulting binary; you never know what CPU or situation someone is in If you want to know how your favourite distribution compiles packages, check `vim --version` to see that they use very mild optimisation settings (-mtune=generic -O2 -pipe).
We might want to look into our configure files, though, to check whether the way how we modify the CFALGS (overwrite, append, prepend) is convenient and/or correct or could be imporoved for both purposes. Suggestions and help are welcome.
I use --disable-everything and set CFLAGS and X_CFLAGS, and that works correctly enough.