On 06/27/2017 11:14 AM, Robert Dailey wrote: > Also at $DAYJOB, we all work on the same code base. Our product is > tested and verified to work on a distinct set of configurations. Why > would I ask each user to create their own toolchain file?
If you have a toolchain file that works in some finite set of tested environments then there is no reason not to share it among them. Why can't the logic to choose `CMAKE_ANDROID_NDK_DEPRECATED_HEADERS` be in your toolchain file? All it needs to know is the NDK location. -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
