The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15050
==
Reported By:Erik Lindahl
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15051
==
Reported By:Erik Lindahl
Assigned To:
The output file regeneration introduced in ad502502 and refined by
38571f2c does not seem to work with the visual studio (tested 2010,
reportedly also 2012) and Ninja generators.
I merged the topic output-tracking which extends the
RunCMake.configure_file test to find out where it actually
On 07/31/2014 06:55 AM, Nils Gladitz wrote:
I merged the topic output-tracking which extends the
RunCMake.configure_file test to find out where it actually does/does not
work.
No need for that. Just do git grep GetOutputFiles and you will
see that no generators even query that except
On 07/31/2014 03:12 PM, Brad King wrote:
On 07/31/2014 06:55 AM, Nils Gladitz wrote:
I merged the topic output-tracking which extends the
RunCMake.configure_file test to find out where it actually does/does not
work.
No need for that. Just do git grep GetOutputFiles and you will
see that no
On 07/31/2014 09:12 AM, Nils Gladitz wrote:
No need for that. Just do git grep GetOutputFiles and you will
see that no generators even query that except Makefile and Ninja.
Therefore Xcode and VS generators are missing this support.
Are they intentionally left out?
I don't think so.
On 07/31/2014 03:38 PM, Brad King wrote:
The problem for VS and Xcode is that these output files may not
be newer than the inputs, so they cannot be simply listed as build
outputs of the rule to re-run CMake or it will run every time.
The Makefile generator solves this with the
On Wed, 30 Jul 2014 18:10:36 -0400, Bill Hoffman said:
I am working on scan-build integration with ctest/CDash and did a build
of CMake. The results show up in the warning section of the build:
http://open.cdash.org/viewBuildError.php?type=1buildid=3429991
Sweet! Looking forward to turning
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15052
==
Reported By:dpantele
Assigned To:
On 07/31/2014 01:21 AM, Leek, Jim wrote:
I recently converted my project to configure with cmake, and am now
trying to get the tests to run under ctest. I may be doing this
completely incorrectly, so let me know if anything you see below looks
like a bad idea.
All my tests use a particular
Hi David,
Thanks.
Background of our project:
In our project there are many modules. The existing build system is using
Microsoft Visual Studio. Each module has a Microsoft Visual Studio project
(.vcxproj) file and in some of the project files, Microsoft Visual Studio
targets (.targets)
CMake itself does this to include a file at ctest time that applies to
*all* tests:
set_directory_properties(PROPERTIES
TEST_INCLUDE_FILE
${CMake_BINARY_DIR}/Tests/EnforceConfig.cmake)
It results in this line being generated in CTestTestfile.cmake at the
very top of the file:
So from the example you've sent, it seems like the stuff in your
targets file is just a bunch of custom commands that you'd need to run.
There are plenty of examples of projects using add_custom_command and
add_custom_target out there, and if you have specific questions about
how those
Hi David,
Thanks for the reply. Understood.
Will use the cmake function add_custom_command() with POST_BUILD option in case
of after build and PRE_BUILD option in case of before build.
Thanks Regards
Ravi Raman
Xoriant Solutions Pvt. Ltd
4th Floor, Winchester, Hiranandani Business Park,
Hello,
I would like to apply the switch /MP[n] for setting the number of
cores to be used in a compilation, however it does not behave
correctly.
If I add /MP4 for example in my${CMAKE_CXX_FLAGS_RELEASE}, cmake
converts it to /MP that means all cores available.
It's like it is not parsing the
On Thu, Jul 31, 2014 at 10:29 AM, Jaime Armendariz wrote:
If I add /MP4 for example in my${CMAKE_CXX_FLAGS_RELEASE}, cmake converts
it to /MP that means all cores available.
[snip]
Cmake 3.0.0 and 2.8.12.2
Windows 7 64 bits
Visual Studio 2013 / Visual Studio 2010 SP1
With CMake 3.0.0 on VS
hi,
when i set CPACK_PACKAGE_RELEASE to :
set(CPACK_PACKAGE_RELEASE )
spec file still stays the same 1 :
Summary:A cache configuration service.
Name: cacheproxyd
Version:1.0.8
Release:1
i see that rpm file name that depends on it changes:
OK, the below suggestion did have one problem, but I was able to make it
work. The problem, kind of hinted at in David Cole's answer, was that,
since the file is run at test time, variables defined at configure time
don't work. So, this did NOT work:
added to top level CMakeLists.txt:
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 d20fa54403c2939bd29bfc97a25b745b6b97c078 (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 7baa9da26052c8261b274be1756ca646f987d633 (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 2ba18f62846735a8c466f0ddfa602a18cea583f8 (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 b056b8c46ced8160190a73a3ecf73606086cf17a (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 ba53bc5a9dd65c4525e0e9e4af86c595710094e0 (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 c1560296db63f4021f6f9e38e3280fad13db9812 (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 ec7470df55bd5744264bb4f810d46ff085369084 (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 b4745001e8f908cb9ae53db29e4120ba8dd6a53f (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 2eda7499d11990b0bcae115031d6e6d427ea74bc (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 b48211d4261840136e750d3d82f195ad48b17a8f (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 dda69ff728f518726d19c3b9f12d9e7f955641f6 (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 c9f984ebe8961c764358ff1e2ea3b2b67e0863f5 (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 a2573c45615d79773455bb9dc75c35c2bc059b74 (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 b6bb564f94488d04428479076bdfc3c220ad4a81 (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 d835f7e28f36029f742128b593dda13bcb2d05f0 (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 66f8a0e90c775b1eec4e625e16a475350653c3a6 (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 48ec39bce49ea2ffaf97e6726a3fa901aaca0eab (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 0fbb6c75b64851e51edbd1695120f826cfde20f1 (commit)
via
20140731)
+set(CMake_VERSION_PATCH 20140801)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
37 matches
Mail list logo
