[CMake] Setting policy to old for CMP0043 does not suppress warning messages

[Jake]

As a last note, I think that this warning behavior should be changed. Now
that I've figured things out, I have 5 total occurrences of
COMPILE_DEFINITIONS_something in my entire project (all CMake files) and I
received 82 warnings.


On Fri, Jun 13, 2014 at 9:53 AM, Jake <thatcadguy at gmail.com> wrote:

> Nevermind, answered my own question. Setting CMP0043 to new at the
> beginning of the main file and then push/popping and setting to old where
> needed produced no warnings.
>
>
> On Fri, Jun 13, 2014 at 9:44 AM, Nils Gladitz <nilsgladitz at gmail.com>
> wrote:
>
>> On 13.06.2014 18:32, Jake wrote:
>>
>>> Hello,
>>>
>>> I upgraded to 3.0 recently and tried to generate build files for a
>>> project (https://github.com/tpaviot/oce/). I noticed the new warning
>>> about CMP0043 and have been trying to fix, but setting the policy to OLD,
>>> even at the beginning of CMakeLists.txt doesn't seem to do anything. Is
>>> this a bug or what? "cmake_policy(SET CMP0043 OLD)" is what I put at the
>>> beginning.
>>>
>>
>> cmake_minimum_required() resets policies to match the version provided.
>> Did you set the policy before or after?
>>
>> Nils
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20140613/ea5608ad/attachment.html>