On 07/31/2015 12:54 PM, Alex Merry wrote:
>> Setting policies centrally breaks their compatibility model.
>
> I should perhaps explain our use case:
My assertion stands regardless of the use case.
> Now, sure, we could change every single project that includes this module to
> use NO_POLICY_SCO
On Thursday 30 July 2015 09:28:12 Brad King wrote:
> On 07/29/2015 03:58 PM, Alex Merry wrote:
> > This is intended to be used from a "settings file" which is applied to a
> > group of CMake projects. This allows the file to control which policies
> > means that users of the settings file are not f
On 07/29/2015 03:58 PM, Alex Merry wrote:
> This is intended to be used from a "settings file" which is applied to a
> group of CMake projects. This allows the file to control which policies
> means that users of the settings file are not forced to use NO_POLICY_SCOPE
> (particularly important if t
Add a PARENT_SCOPE argument to cmake_policy(SET) that makes the policy
apply to the parent (strong) scope - it will break out of exactly one
level of the policy stack.
This is intended to be used from a "settings file" which is applied to a
group of CMake projects. This allows the file to control
