The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15081
==
Reported By:ycollet
Assigned To:
Hi Roger,
Thanks for the revisions!
On 08/12/2014 05:59 PM, Roger Leigh wrote:
Regarding the Windows Registry, I've taken a look and it looks
like there might be some usable keys from the installer which
could be used, but I'll need to do further digging with all
the different versions to
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15082
==
Reported By:ycollet
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15085
==
Reported By:tim blechmann
Assigned To:
Hi Marco.
Sane compilers allow later command-line options to override earlier ones,
so what you're doing should be fine. Unfortunately, I know some Fortran
compilers are not sane in this regard.
If you really need to solve this by explicitly modifying the global list
for a particular file, the
Hi Petr,
thanks, very informative!
2014-08-13 9:20 GMT+0200, Petr Kmoch petr.km...@gmail.com:
Hi Marco.
Sane compilers allow later command-line options to override earlier ones,
so what you're doing should be fine. Unfortunately, I know some Fortran
compilers are not sane in this regard.
Hi,
I’m using ExternalProject, but the documentation does not really reflect what I
am witnessing
I have a Project X which is included through ExternalProject in Project A
Project X has no PREFIX set in its CMakeLists
I include project X like this:
include(ExternalProject)
If x is a CMake-driven project, you'll also need to explicitly set
CMAKE_INSTALL_PREFIX when configuring. If not, there's likely a
--prefix arg for configuring... One of those also has to be set to
install to a non-default location.
The PREFIX arg for ExternalProject is only used to organize
See, for example:
https://github.com/OpenChemistry/openchemistry/blob/master/CMakeLists.txt#L24
A common CMAKE_INSTALL_PREFIX is used for all OpenChemistry
ExternalProject builds that are driven by CMake.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
I see thanks, so install_dir has a different meaning than the eventual install
dir of the external project, I thought there would be some ‘magic’ where the
ExternalProject functions would override the the prefix of, in this case,
project x.
I still have one issue, perhaps I should start a new
On Wed, Aug 13, 2014 at 3:18 AM, marco restelli mreste...@gmail.com wrote:
Hi Petr,
thanks, very informative!
2014-08-13 9:20 GMT+0200, Petr Kmoch petr.km...@gmail.com:
Hi Marco.
Sane compilers allow later command-line options to override earlier ones,
so what you're doing should
If project Y needs to link to project X, you could build project Y with
ExternalProject_Add and list project X in the DEPENDS parameter.
http://www.cmake.org/cmake/help/v3.0/module/ExternalProject.html
On Wed, Aug 13, 2014 at 9:39 AM, Hans van den Bogert hansbog...@gmail.com
wrote:
I see
2014-08-13 15:53 GMT+0200, Mark Abraham mark.j.abra...@gmail.com:
On Wed, Aug 13, 2014 at 3:18 AM, marco restelli mreste...@gmail.com
wrote:
Hi Petr,
thanks, very informative!
2014-08-13 9:20 GMT+0200, Petr Kmoch petr.km...@gmail.com:
Hi Marco.
Sane compilers allow later
On Wed, Aug 13, 2014 at 7:12 AM, marco restelli mreste...@gmail.com wrote:
2014-08-13 15:53 GMT+0200, Mark Abraham mark.j.abra...@gmail.com:
On Wed, Aug 13, 2014 at 3:18 AM, marco restelli mreste...@gmail.com
wrote:
Hi Petr,
thanks, very informative!
2014-08-13 9:20 GMT+0200,
2014-08-13 16:16 GMT+0200, Mark Abraham mark.j.abra...@gmail.com:
On Wed, Aug 13, 2014 at 7:12 AM, marco restelli mreste...@gmail.com
wrote:
2014-08-13 15:53 GMT+0200, Mark Abraham mark.j.abra...@gmail.com:
On Wed, Aug 13, 2014 at 3:18 AM, marco restelli mreste...@gmail.com
wrote:
Hi
Are these actually C++ files? If so then they should really have a C++
extension (like .cp or .cxx). It may be a good idea in general since other
build tools may run in to the same sort of issue of assuming they are C
files. A few other tips: first, by placing all your source files in a list
Hello,
For our Continuous Integration tests we need fast incremental builds
(only build what has changed).
This also includes that CMake only has to run if necessary (some
CMakeLists.txt changed).
It seems there is no beautiful/portable/generator-independent way to do
this?!
Fortunately we
On Wed, 2014-08-13 at 21:40 +0200, Nagger wrote:
Does anyone already came up with a good solution? Isn't this a common
problem?
I'm not sure about the other generators, but the makefile generator has
this built-in; that is, if the makefiles detect that a cmake file has
changed it will re-run
Am 13.08.2014 21:59, schrieb Paul Smith:
On Wed, 2014-08-13 at 21:40 +0200, Nagger wrote:
Does anyone already came up with a good solution? Isn't this a common
problem?
I'm not sure about the other generators, but the makefile generator has
this built-in; that is, if the makefiles detect that
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 c4cf702d727cb140986b2c21e67470457849f791 (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 457cf2d45d9375dc0d364afe3162495f810546d5 (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 a776a67a07f057be07da744532b239781889bfc4 (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 c56712addae8000900b9820768104724e99b4aa8 (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 e6199640525bda0327cc6da6dc48fe8d26c7a8d3 (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, release has been updated
via 302ba3f71ac43947ae296421aa5be22d9342a63e (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 5c047211a5e933fd4d30a2956800742686464c97 (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 1c7089924e6240a1af6e50c097023f5898687733 (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 427f096751763b1b94e4303d27713e8ce3ca06ec (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 91d45dd1ef90f8a56689eda81e768e61db3905b6 (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 3b10600e60b9f24bea1bcfbca0dda5a93ecc9085 (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 3a3bdd27d79a9f732a7afe90b2b705b1b0f57ea6 (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 1bfdb1deb286a6dd148797f4141b930847877639 (commit)
via
20140813)
+set(CMake_VERSION_PATCH 20140814)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
33 matches
Mail list logo
