<html><body>
<p><font size="2" face="sans-serif">Thanks for the response. None of those are called in the CMakeLists.txt file that the warning is issued for, they are both called in a file above that one in the build tree but said file also sets the CML0028 policy afterwards. Is it possible that a call to cmake_minimum_required resets the policies even for CMakeLists.txt that are not below it in the build system tree?</font><br>
<br>
<font size="2" face="sans-serif">Regards,</font><br>
<font size="2" face="sans-serif">Pierre Andersson</font><br>
<br>
<br>
<img width="16" height="16" src="cid:1__=4EBBF781DFACCDC38f9e8a93d@atlascopco.com" border="0" alt="Inactive hide details for Nils Gladitz ---2014-07-11 11:31:20---On 07/11/2014 11:00 AM, pierre.andersson@se.atlascopco.com wrot"><font size="2" color="#424282" face="sans-serif">Nils Gladitz ---2014-07-11 11:31:20---On 07/11/2014 11:00 AM, pierre.andersson@se.atlascopco.com wrote: > I have a very large project that</font><br>
<br>
<font size="1" color="#5F5F5F" face="sans-serif">From: </font><font size="1" face="sans-serif">Nils Gladitz <nilsgladitz@gmail.com></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">To: </font><font size="1" face="sans-serif">pierre.andersson@se.atlascopco.com, cmake@cmake.org</font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Date: </font><font size="1" face="sans-serif">2014-07-11 11:31</font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Subject: </font><font size="1" face="sans-serif">Re: [CMake] Setting Policy CMP0028</font><br>
<hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br>
<br>
<br>
<tt><font size="2">On 07/11/2014 11:00 AM, pierre.andersson@se.atlascopco.com wrote:<br>
> I have a very large project that is built with CMake, and I'm trying to<br>
> make it work a little nicer with CMake 3. Right now we, we see everal<br>
> warnigns that policy CMP0028 is not set.<br>
><br>
> Using<br>
><br>
> cmake_policy(SET CMP0028 OLD)<br>
><br>
> does not seem to take effect. It's set at the same, top level, place<br>
> where other policies are set and these do take effect. Likewise, setting<br>
> the policy to NEW does not make CMake produce the fatal error like the<br>
> documentation says it should. What am I missing here?<br>
<br>
With a minimal test case the policy seems to work for me in 3.0.<br>
<br>
What might reset the policy after it was set is:<br>
- A call to cmake_minimum_required()<br>
- A call to cmake_policy(VERSION)<br>
<br>
Nils<br>
</font></tt><br>
</body></html>