Brad King wrote: >> Additionally I've added a commit to >> my clone in the error-on-exported-missing-include-dir branch, which >> introduces a policy. That commit doesn't really have to be in CMake >> 2.8.11. Currently the test doesn't pass, and I'm not sure why. The >> cmake_policy() line in the test doesn't seem to have an effect.
> The switch on GetPolicyStatus does not use our standard convention. > Usually we have WARN fall through to OLD and have NEW as its own case. > Currently I think it is right but hard to follow. Can you refactor? > > I don't see at a glance why the test would fail. You'll have to dig. I solved this by recording the policy status when the target is created. The policy stack seems to be popped after the configuration step is done, so my new setting was being lost. Thanks, Steve. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
