On 03/11/2014 10:43 AM, Daniele E. Domenichelli wrote: > It is a quite common use case to get and set "path" environment
It is not very common within CMake's own modules: $ git grep TO_NATIVE_PATH v3.0.0-rc1 -- Modules |wc -l 2 $ git grep TO_CMAKE_PATH v3.0.0-rc1 -- Modules |wc -l 24 # (and 6 of these are in one module) We don't like to have behavior depend on environment variables more than necessary. They may not still be set when CMake re-runs inside the build system. That is one reason we CACHE the find results. Setting an environment variable for a tool that runs under CMake is a pretty special case in this topic. -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/cgi-bin/mailman/listinfo/cmake-developers
