Hi Chris,
> One of my co-workers likes to start multiple makes in various parts of his
> project source tree. Under our old Makefile-based, build-in-source system,
> this worked fine. Under our new CMake-based, out-of-source build system, this
> causes problems, since any make might cause CMake to rebuild its internal
> files.
>
> Is this a "don't do that" problem, or can CMake be used in a manner where it
> is smart enough not to step on its own toes?
One workaround would be to run cmake manually before setting off multiple "(cd
blah; make)" processes in the background. CMake should not need to run multiple
times per "make" invocation unless you are doing something very strange.
Also, if you are using your personal knowledge of project dependencies and know
it is OK to skip some steps, you might try making the "/fast" version of
targets in those subdirectories without rebuilding their indirect dependencies
(e.g., if "make foo" works, you can "make foo/fast" to avoid rebuilding other
targets that foo depends on). I am less sure that this avoids re-runs of CMake,
but I don't recall it doing that in general.
David
--
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
