On 05/13/2017 08:55 PM, Craig Scott wrote: > only set on the CMake command line by CI builds or similar,
Correct. We need a way to activate such tests only on machines where we expect them to work. It would be nice to have something better but I'm not sure what else we can do. We used to try to add tests for find modules automatically but that ends up needing to run the find modules as part of configuring CMake, giving the false appearance that CMake actually needs all those packages and possibly breaking on bad ones. The GTK2 tests still have this problem. -Brad -- 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
