On Tue, Jan 20, 2015 at 10:42:47 -0500, Daniel Levin wrote: > This wrapper script cannot be common, because for each kind of build env > variable set will be different. So it need to be created at CMake > generation time saving current QNX* env variables into this wrapper script. > So next time you can open clean shell and run 'make' or 'ninja' and it will > properly use environment variables defined previously at generation stage.
What if Ninja itself gained support for 'env =' on rules for Ninja to set environment variables for the rule and QNX-on-Windows set CMake variables which filled this in appropriately? --Ben -- 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
