Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On 09/26/2011 01:15 PM, Marc-André Laverdière wrote:
I tried doing that, but it seems that my autogen flags made it so that I
was compiling some module unknown to me that was in 'build warning land'.

Unless we don't have modules living in such countries anymore, I won't
want to enable that option.

I see this flag as an aspirational goal "let us fix all that stuff so
that we can -one day- compile everything that way"

We were there already, and I think we still are there (at least on Linux with recent GCC, maybe it decayed on Windows).

I personally am against anything that makes it harder for a n00b like me
to get something done. The learning curve is not-so-easy so lets not
make it worse.

For just compiling the sources, the default of --disable-werror is hence the way to go. For actually making changes to the code, and especially doing so as a newbie -- what's wrong with the help offered by those compiler warnings? (Given they are caused by your changes, not by code that was already dirty with warnings before you touched it -- which brings me back to the point that all developers should use --enable-werror all the time, to keep the master clean.)

-Stephan

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.