2011/2/2 Emmanuel Blot <eblot...@gmail.com>:
>> Currently, there is no way to turn this off.
>
> Very, very bad news ;-(
> IMHO, this is a recurrent issue with CMake. It seems there is no way
> to guarantee that a project that builds well with a version of CMake
> will build the same way with the next minor iteration (used to be
> called "patch release").
I think "recurrent" is a relatively tough statement, I'm using
CMake for 7+ years now and never get caught by such an issue.
I think that, CMake developpers are indeed very concerned with
backward compatibilty.
POLICY are made for that.
CMake test suite and related dashboard are there too.
The fact is sometimes you can not imagine what people do with the software
you make :-]
So breakage during RC is not that bad.
>From my point view this reveals two things:
- the whole CMake test suite is not covering enough use case
but there is no so much people volunteering for enhancing the test suite
- There is a a lot of enhancement request for CMake coming
from the community so CMake urgently need new stringent builtin
checks in order to avoid the "noise of misusage"
(no blame to anyone just a feeling from reading the ML)
> Adding new options, new error detections to CMake is great, but
> turning on these new features by default is often a source of issues.
> We cannot control which minor release of CMake a client uses to build
> up an application. Controlling a major version is ok (2.6 vs. 2.8),
> but controlling a patch release is impossible, as CMake gets
> automatically updated in Linux distributions, for example.
In the end, I off course agree with you that one should avoid such
"default new behavior", I think in this case it is
possible so may be switching those warning off by default would
be the way to go for 2.8.4 (my personal opinion though).
>> The idea was to catch misspelled words.
>
> The idea is definitely nice, but why do not turn on this kind of new
> policies on explicit request (either with a new option switch and/or a
> new POLICY statement) as long as CMake does not reach a new major
> milestone?
> Dealing with the constant modifications of CMake options is a tough
> job for a software maintainer, I believe.
Dealing with constant user request is a tough job for developers too,
Just kidding :-]
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
