On 04/19/2012 11:40 AM, SF Markus Elfring wrote: >> are you really proposing to add -Werror by default? >> >> Sure, it has its value if you fully control the build environment e.g. >> for the maintainers / developers of the application. But for users of >> the code it is a good way to turn some away as they cannot even compile >> your code. > > Do you distinguish this warning option for the tool "automake" from a > similar parameter that can be passed to compilers? No, it looked like the gcc options and that's why I asked. But that kinda would explain it why in the past I couldn't build some software that didn't provide a configure file but made me jump though automake/autoconf hoops.
I'm siding with the coccinelle maintainers on this one: "automake is not the answer. automake is the question. The answer is: No." > http://www.gnu.org/software/automake/manual/html_node/amhello_0027s-configure_002eac-Setup-Explained.html#index-g_t_002dWerror-83 > > > Do other maintainers, software developers and packagers fiddle also with > build specifications that we are discussing here? >From my experience with Wine the build system is something that very very seldom needs to change. And then one has to relearn again any fancy build system; so KISS wins out big time. E.g. Wine uses autoconf but not automake. Adding a short simple Makefile.in is all that's needed so that is done even by Wine people that don't consider them self to be developers. bye michael _______________________________________________ Cocci mailing list [email protected] http://lists.diku.dk/mailman/listinfo/cocci (Web access from inside DIKUs LAN only)
