On 01/20/2015 01:04 PM, Daniel Levin wrote: > Brad King wrote: >> We expect that environment variables required by the toolchain >> in use are already loaded. > configure everything once, save into cache, build with single > invocation of build tool
Use of a developer-provided environment was a very early and quite fundamental design decision, and is unlikely to be changed. I'd rather this discussion focus on how to get a sh-based ninja working for your environment. Unfortunately without access to such an environment myself I do not understand it well enough to suggest the best approach. Can you provide sample ninja build files (perhaps hand written) that demonstrate invocations of the compiler and other tools, assuming it runs with the proper environment already defined? -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
