On 08/26/2010 03:43 PM, Alexander Neundorf wrote: >> It will break too much code. If we give a warning and continue that >> should be fine.
As Alex points out, a policy will do this by default. > So, no policy ? If you are willing to put in the effort then a policy is the correct solution. > With a policy it would warn and continue, except when the policy is > set to NEW, then it would fail. ...and eventually it will always be set to NEW when calls to cmake_minimum_required(VERSION) are updated. Notice how rarely questions about CMP0003 come up these days because it is auto-set to NEW in most projects now. We've moved on from the old behavior completely in only a couple years :) -Brad _______________________________________________ cmake-developers mailing list [email protected] http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
