The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15326
==
Reported By:Kwabena W. Agyeman
Assigned To:
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
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
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?
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
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,
this
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
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.
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 889e889a0377d047dd4430cd4e5f7f29d81d274e (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 2a9f3dc6c7aed366d8dda71038bdc2b62e4fa78a (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 661622f011810093433afa5c9a4795b3d2f19070 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via c20d3d319cb97da5793beebe42a80361b2d247c4 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 52ee1946b9f25e8cc7befec9276b2d5379ebf92d (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via d4c7b08bf72e733f63b10fa989466e3065cbaca6 (commit)
via
20141224)
+set(CMake_VERSION_PATCH 20141225)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
15 matches
Mail list logo
