[cmake-developers] User vs CMake include mismatch handling

[Marcel Loose]

>>> On 18-11-2010 at 14:43, in message <4CE52D91.7070902 at kitware.com>,
Brad King
<brad.king at kitware.com> wrote: 
> On 11/18/2010 04:29 AM, Marcel Loose wrote:
>> I've been following this discussion with interest for quite a while.
I
>> was wondering if both worlds could be united (Alex's and David's) if
it
>> were possible to set cmake_minimum_required on the command line?
That
>> way Alex can be happy, because he doesn't have to modify
CMakeLists.txt
>> files - something he cannot do for previous KDE releaeses; and
David
>> will be happy, because old projects will not suddenly break due to
some
>> incompatible changes in CMake.
> 
> Even if it could be set from the command line then the first call
> to cmake_minimum_required will change it back.  We can't just make
> all calls ignore their argument and use the value from the command
> line because there can be many calls to in different subdirectories
> and modules.  The entire point of a call to cmake_minimum_required
> is to say "I was written with this version of CMake in mind".
> 
>> BTW: IMHO this new policy should default to NEW for CMake 2.8.4 and
>> later, but I think that's what David suggested as well.
> 
> See here for the purpose of policies:
> 
>   http://www.cmake.org/Wiki/CMake_Policies
> 
> Policies absolutely *MUST* default to WARN, no "if-s, and-s, or
but-s" about
> it.  If that does not work for this case then a policy is not the
solution.
> 

Hi Brad,

Thanks for the pointer to policies.

Slightly off-topic: I couldn't find any references to this information
in the CMake manual. It would also be nice if you could easily check
which policies are set (and to which value) for a given project. AFAIK
there's currently no way to get this information, right?

Best regards,
Marcel Loose.