On 06/16/2010 05:01 PM, Andreas Mohr wrote:
What's so problematic about having isolated build directories (out-of-tree) for multiple configurations?
Because it is *different* from IDE-backends such as Visual Studio. I have no problems with having multiple build trees per se, but having completely different ways of building multiple configurations forces any driving build script to have to know whether to run CMake once for all configurations or once per configuration.
If the "cmake --build" mechanism could be extended to automatically build all configurations (by for example creating (on Unix) multiple per-configuration build trees under the "root" build tree), that would be a sufficient solution for me.
-- Jesper Eskilson Developer IAR Systems http://www.iar.com _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
