On 04/27/2015 03:31 PM, Brad King wrote:
The policy was added to diagnose some previously-broken cases earlier.
We technically never supported duplicate MAIN_DEPENDENCY specification
but did not diagnose it. Instead it could produce bad builds in some
cases IIRC.
Nils, do you remember where this came up?
I think I covered this in:
http://www.cmake.org/Bug/view.php?id=15525#c38598
Issues I know of (two of which I reported; including the above) are:
http://www.cmake.org/Bug/view.php?id=14550
http://www.cmake.org/Bug/view.php?id=15434
http://www.cmake.org/Bug/view.php?id=15525
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
