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
inter
Am Mittwoch, 24. Dezember 2014, 10:17:07 schrieb Chris Johnson:
> 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,
> thi
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 t
On 2014-12-24 11:07-0600 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
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 t
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 CMak