The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=13488
==
Reported By:Stanislav Ravas
Assigned To:
Hello,
I have split my changes in a series of small patches. Please find them
in attachment.
I have made sure that everything is compiling correctly and that the
CTest.UpdateSVN test runs successfully between each of them.
Some comments about the testing:
- Most of the code path added by these
On 08/24/2012 08:50 AM, Xavier Besseron wrote:
I have split my changes in a series of small patches. Please find them
in attachment.
I have made sure that everything is compiling correctly and that the
CTest.UpdateSVN test runs successfully between each of them.
Very nice, the series looks
Go CMake!
- sent from my open source android phone.
-- Forwarded message --
From: Jordan Rose jordan_r...@apple.com
Date: Aug 24, 2012 4:28 PM
Subject: [cfe-dev] Warm Fuzzies
To: cfe-...@cs.uiuc.edu Developers cfe-...@cs.uiuc.edu
Now that the mailing list is back up, I can share
2012/8/24 Jason T. Slack-Moehrle slackmoeh...@gmail.com:
Hello
OS X 10.8, CMAKE 2.8.9.
In CMAKE 2.8.9 it seems that CMAKE_FILES_DIRECTORY
SET( PROJECT_BINARY_DIR . )
SET( CMAKE_FILES_DIRECTORY ${PROJECT_BINARY_DIR}/output/CMakeFiles )
SET( EXECUTABLE_OUTPUT_PATH ${PROJECT_BINARY_DIR}/bin
Hi,
i use install(FILE ..) to install a configuration file config.txt by both
RPM packages A.rpm and B.rpm, due to the name and version in config.txt, the
config.txt is not exactly the same in A.rpm and B.rpm. Now I've got an file
conflict error when A.rpm was installed, B.rpm failed the
2012/8/24 hce jupiter@gmail.com:
Hi,
i use install(FILE ..) to install a configuration file config.txt by both
RPM packages A.rpm and B.rpm, due to the name and version in config.txt, the
config.txt is not exactly the same in A.rpm and B.rpm. Now I've got an file
conflict error when
Hi all,
I started using CMake, CTest and CDash, with the simple targets Nightly,
Continuous and Experimental: it works very well.
Now I would like to divide my project in subproject, so that a failure in
compiling one small test is not affecting the full dashboard report. I read
that ctest driver
I set the build name and site in my CMakeLists.txt before calling
include(CTest) and it works.
Sent from my iPhone
On Aug 24, 2012, at 9:01, Michele Dolfi dolfim...@gmail.com wrote:
Hi all,
I started using CMake, CTest and CDash, with the simple targets Nightly,
Continuous and
On Fri, Aug 24, 2012 at 9:07 AM, Leif Walsh leif.wa...@gmail.com wrote:
I set the build name and site in my CMakeLists.txt before calling
include(CTest) and it works.
But then you can only submit dashboards from one site with that CMakeLists
file...? Anybody else submitting a dashboard for
They are generated from facts I detect about the os
Sent from my iPhone
On Aug 24, 2012, at 9:24, David Cole david.c...@kitware.com wrote:
On Fri, Aug 24, 2012 at 9:07 AM, Leif Walsh leif.wa...@gmail.com wrote:
I set the build name and site in my CMakeLists.txt before calling
On Fri, Aug 24, 2012 at 9:34 AM, Leif Walsh leif.wa...@gmail.com wrote:
They are generated from facts I detect about the os
Ah ok. Better then. :-)
You could do the same thing in a ctest script. A lot of the projects we
work on at Kitware share a common script for the project that is
On Fri, Aug 24, 2012 at 3:24 PM, David Cole david.c...@kitware.com wrote:
On Aug 24, 2012, at 9:01, Michele Dolfi dolfim...@gmail.com wrote:
Hi all,
I started using CMake, CTest and CDash, with the simple targets
Nightly, Continuous and Experimental: it works very well.
Now I would
On Fri, Aug 24, 2012 at 9:45 AM, Michele Dolfi dolfim...@gmail.com wrote:
On Fri, Aug 24, 2012 at 3:24 PM, David Cole david.c...@kitware.comwrote:
On Aug 24, 2012, at 9:01, Michele Dolfi dolfim...@gmail.com wrote:
Hi all,
I started using CMake, CTest and CDash, with the simple
Hello everyone,
I have tried asking this question on stackoverflow [1] without much
luck, so here we go:
My project links to a third-party library that comes with a valgrind
suppression file, as well as a CMake script. The script stores the
location of the suppression file in a CMake cache
Then I cannot use the subproject separation, right?
It seems this is feature that got lost with the new style:
http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest#Continuous_Builds_.28old_Style.29
Michele
On Fri, Aug 24, 2012 at 3:51 PM, David Cole david.c...@kitware.com wrote:
On Fri, Aug 24,
Hi Eric,
OS X 10.8, CMAKE 2.8.9.
In CMAKE 2.8.9 it seems that CMAKE_FILES_DIRECTORY
SET( PROJECT_BINARY_DIR . )
SET( CMAKE_FILES_DIRECTORY ${PROJECT_BINARY_DIR}/output/CMakeFiles )
SET( EXECUTABLE_OUTPUT_PATH ${PROJECT_BINARY_DIR}/bin )
I dont see an 'output/CMakeFiles' created but I do
2012/8/24 Jason T. Slack-Moehrle slackmoeh...@gmail.com:
Hi Eric,
OS X 10.8, CMAKE 2.8.9.
In CMAKE 2.8.9 it seems that CMAKE_FILES_DIRECTORY
SET( PROJECT_BINARY_DIR . )
SET( CMAKE_FILES_DIRECTORY ${PROJECT_BINARY_DIR}/output/CMakeFiles )
SET( EXECUTABLE_OUTPUT_PATH
On Fri, Aug 24, 2012 at 9:46 AM, Davide Mancusi are...@gmail.com wrote:
Hello everyone,
I have tried asking this question on stackoverflow [1] without much
luck, so here we go:
My project links to a third-party library that comes with a valgrind
suppression file, as well as a CMake script.
On Fri, Aug 24, 2012 at 10:42 AM, David Cole david.c...@kitware.com wrote:
On Fri, Aug 24, 2012 at 9:46 AM, Davide Mancusi are...@gmail.com wrote:
Hello everyone,
I have tried asking this question on stackoverflow [1] without much
luck, so here we go:
My project links to a third-party
Hello all,
I'm relatively new to CMake but I've encountered some unexpected behavior.
Perhaps it's by design or perhaps it's a bug - you tell me. The short story is
this:
It appears that add_custom_command() is ignored if the only OUTPUT is a C
header file (.h). The generated makefiles do
Adam B wrote:
Hello all,
I'm relatively new to CMake but I've encountered some unexpected behavior.
Perhaps it's by design or perhaps it's a bug - you tell me. The short
story is this:
It appears that add_custom_command() is ignored if the only OUTPUT is a C
header file (.h). The
Hi,
On Fri, Aug 24, 2012 at 7:27 PM, Adam B ad...@videx.com wrote:
Hello all,
I'm relatively new to CMake but I've encountered some unexpected behavior.
Perhaps it's by design or perhaps it's a bug - you tell me. The short story
is this:
It is a bug, but not in CMake, its in your cmake
Hi,
I'm trying to get up and running with CMake for a project I'm working
on. The online documentation seems to describe how to write the
script/configuration files; I'm trying to first get my head around a
more basic overview.
Suppose I have a minimal project called foo, that just consists of a
On Friday 24 August 2012, Russell Wallace wrote:
Hi,
I'm trying to get up and running with CMake for a project I'm working
on. The online documentation seems to describe how to write the
script/configuration files; I'm trying to first get my head around a
more basic overview.
Suppose I
2012/8/24 Russell Wallace russell.wall...@gmail.com:
Hi,
I'm trying to get up and running with CMake for a project I'm working
on. The online documentation seems to describe how to write the
script/configuration files; I'm trying to first get my head around a
more basic overview.
There
On 08/24/2012 11:09 AM, Andreas Pakulat wrote:
Hi,
On Fri, Aug 24, 2012 at 7:27 PM, Adam Bad...@videx.com wrote:
Hello all,
I'm relatively new to CMake but I've encountered some unexpected behavior.
Perhaps it's by design or perhaps it's a bug - you tell me. The short story
is this:
It
Thanks! That's clearer now. I guess using a separate build
subdirectory has an advantage in that if something goes wrong you can
just scrub that whole subdirectory and try again.
a couple of dead links from http://www.cmake.org/Wiki/CMake#Tutorials
- the following give 404:
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 6dab13c56e731d3d8ed6a751a6e0735835acc76f (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 bc147d99caa9186b2dc0a431bd6c0f49a1ded594 (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 6d4a3053e63e00f0b0d002ddecd81ff489c97355 (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 4f7731d814d4228165c70ec9fd6b580e5541ddc6 (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 56591cb9b4f1caa62cde98dedf6eb1a0dc7d8d8d (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 a9a3b3b8972d741d1607e25b1ee5739742e9cb6c (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 38876a39036eaa2bdcc187aac93c96c6e8d6c95f (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 4ac85d07766ff2bb51493b0f6ddcef2cb59805e4 (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 db78df744f71cada436c21499cc22a86554a6de4 (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 34a0284603e3f4c746140d4c94eab98f9e513a8d (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 8d6c1ced286ffbf4f50384273b186cc60bd747d3 (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 f84d7b95ebcfa32c02f8b9651b3729be2e936c77 (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 7cf38c892120874285383f1f58ac6b3e0d3fd5fb (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 3fe05b56ecc9857504a6699d702f9377e430ee1c (commit)
via
Stamp
diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 3bdb60c..72ed577 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -2,5 +2,5 @@
set(CMake_VERSION_MAJOR 2)
set(CMake_VERSION_MINOR 8)
set(CMake_VERSION_PATCH 9)
-set(CMake_VERSION_TWEAK 20120824
43 matches
Mail list logo
