Policy old or new

[timothy]

OK, thanks Christian.
Regards


On Fri, 2017-03-03 at 11:13 +0100, Christian Dávid wrote:
> Hi Timothy,
> 
> Jack is right. As non developer you can typically ignore all policy warnings. Maybe you want to use -Wno-dev as argument for cmake, then they should disappear.
> 
> If you want to help us, you can determine which version we want to use. Typically it should be NEW (here, too).
> 
> Greetings
> Christian
> 
> > Jack <ostroffjh at users.sourceforge.net> hat am 12. Februar 2017 um 21:02 geschrieben:
> > 
> > 
> > I hate to say it, but I have always ignored such warnings with no  
> > apparent ill effects.  I think it's something for the developers to  
> > consider, but they are putting all effort towards the Frameworks  
> > version.
> > 
> > Jack
> > 
> > 
> > On 2017.02.11 07:28, timothy wrote:
> > > Debian Mint LMDE-2 Betsy
> > > KMyMoney 4.8.0-9c360433f5
> > > Using KDE Development Platform 4.14.2
> > > cmake version 3.6.2
> > > 
> > > Hi
> > > 
> > > I have compiled the above current kmm version successfully, but with a
> > > myriad of policy warnings.
> > > 
> > > After running 'cmake --help-policy CMP0064' as suggested. I get the
> > > following:
> > > 
> > > CMake version 3.6.2 warns when the policy is not set and uses
> > > ``OLD`` behavior.  Use the ``cmake_policy()`` command to set
> > > it to ``OLD`` or ``NEW`` explicitly.
> > > 
> > > Could someone kindly explain how to set the policy and whether it  
> > > should
> > > be set to OLD or NEW?
> > > 
> > > Many thanks
> > > Regards
> > > Timothy