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
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
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
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
Has anyone out there used CMake to build a PHP Phar file, and more
interestingly, used CMake to install a PHP project which uses Composer for
dependency management?
If so, could you share some information about what your custom commands and
custom targets must look like to get this to work?
Thank
On Tue, 2014-12-23 at 21:32 +, Parag Chandra wrote:
> Have you tried the CMake variables LIBRARY_OUTPUT_PATH and
> EXECUTABLE_OUTPUT_PATH? I¹ve been using them to accomplish much the
> same thing.
Well, I don't want ALL my executables and libraries to go into these
locations. Only specific on
On Tue, 2014-12-23 at 16:59 -0500, David Cole wrote:
> Are you sure there's a problem using TARGET_FILE in your original
> context?
> You should be able to use that in a custom command in your custom
> stage_tgt target...
>
> You have to give the name of the target for the TARGET_FILE generator
>
