On 12/24/2014 05:07 PM, Chris Johnson wrote:
Perhaps I need to clarify.
It's a very large project with many directories and interdependent
libraries. So he is starting a make in one library, and then working on
a program in another subtree of the same project, and running a make there.
Since the entire project shares just one large build tree out-of-source,
both compiles share the same CMakeCache.txt and CMakeFiles/*.
This is not a case of "parallel" makes (-j N) started from one directory.
I don't know if this will help, but as no one managed to provide any
useful tip, here's my 0,02€:
Wouldn't it be possible to write a Makefile that managed all concurrent
builds by calling the relevant make commands for each subproject?
--
Zé
--
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
