The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=12946
==
Reported By:Artur Kedzierski
Assigned To:
The stage is intended only for topics that are imminently going to be
merged to 'next'...
The following CMake topic branches have been on the stage for quite some
time without being merged to 'next':
UseEnabledLanguagesForDirectoryInformationFileIncludePath | master=0 next=0
2012/2/8 David Cole david.c...@kitware.com:
The stage is intended only for topics that are imminently going to be merged
to 'next'...
The following CMake topic branches have been on the stage for quite some
time without being merged to 'next':
I would like to exclude third party header files from the coverage
output. We're using ctest, cmake (version 2.8.5) and cdash, all on
Linux. The archive layout is as follows:
/
/Code/
/Code/Application/
/Code/Application/src/
/Code/Third-Party/
/Code/Third-Party/boost/
On Tuesday 07 February 2012 13:01:49 David Cole wrote:
2012/2/7 Nicolas Desprès nicolas.desp...@gmail.com:
On Sat, Dec 10, 2011 at 3:46 PM, Andreas Schneider a...@cryptomilk.org
wrote:
On Saturday 29 October 2011 23:34:50 Frank Glinka wrote:
Hi,
Hi,
Hi,
I am happy about the
I would like to exclude third party header files from the coverage
output. We're using ctest, cmake (version 2.8.5) and cdash, all on
Linux. The archive layout is as follows:
/
/Code/
/Code/Application/
/Code/Application/src/
/Code/Third-Party/
/Code/Third-Party/boost/
On 02/08/2012 12:00 PM, Rolf Eike Beer wrote:
I would like to exclude third party header files from the coverage
output. We're using ctest, cmake (version 2.8.5) and cdash, all on
Linux. The archive layout is as follows:
/
/Code/
/Code/Application/
/Code/Application/src/
/Code/Third-Party/
Dear Cmake List,
we would like to include a CmakeCache.txt file into our shared
library. The reason is, that we would like to know what CMake options
were used when compiling the library in case we have only the binary.
Has anyone done something like this before and can give me some
pointers?
Dear Cmake List,
we would like to include a CmakeCache.txt file into our shared
library. The reason is, that we would like to know what CMake options
were used when compiling the library in case we have only the binary.
Has anyone done something like this before and can give me some
pointers?
Hi,
I'm not sure if I understand you correctly, but I would guess that in most
cases you don't need to know _all_ cmake cache variables at runtime.
If you really just need to know some specific variables, you would be much
better off using a generated header file. See the documentation for
* Johannes Zarl johannes.z...@jku.at [120208]:
Hi,
I'm not sure if I understand you correctly, but I would guess that in most
cases you don't need to know _all_ cmake cache variables at runtime.
If you really just need to know some specific variables, you would be much
better off using
On Wed, Feb 8, 2012 at 3:20 AM, Andreas Schneider a...@cryptomilk.orgwrote:
On Tuesday 07 February 2012 13:01:49 David Cole wrote:
2012/2/7 Nicolas Desprès nicolas.desp...@gmail.com:
On Sat, Dec 10, 2011 at 3:46 PM, Andreas Schneider a...@cryptomilk.org
wrote:
On Saturday 29 October
I had a hard time following these questions. It sounds like you're
asking the following:
1) Can you set things up so that F7 does a full build and then
automatically does the INSTALL target build?
2) Can you set things up so that you can build a sub project and
have it install just
What I'm asking for is 1) or Can you set things up so that F7 does a full
build and then automatically does the INSTALL target build?
Developers in my team have expressed a need to hit F7 during they're day to day
work and the resulting being the INSTALL target.
This is not a general change I
On 2/7/2012 6:19 PM, Robert Dailey wrote:
+1 to this as well
My bad. I will get to it this week. They don't make it that easy...
-Bill
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages
I wonder if you could do something like:
set_target_properties(INSTALL PROPERTIES EXCLUDE_FROM_DEFAULT_BUILD 0
)
Aaron Meadows
From: david_bjorn...@agilent.com [mailto:david_bjorn...@agilent.com]
Sent: Wednesday, February 08, 2012 9:44 AM
To: Meadows, Aaron C.; cmake@cmake.org
I've tried similar techniques with ADD_DEPENDENCIES to ALL_BUILD and the
trouble with this, within a single project these targets are not generated yet
and you would have to change CMake's C++ code to change this type of behavior.
CMake Error at CMakeLists.txt:231 (set_target_properties):
Ah, that makes sense. Wonder how hard it would be to add a
Pseudo-target to CMake for the targets it will build, and allow the
scripts to set some properties on them which would be imported later as
they are created...
Aaron Meadows
From: david_bjorn...@agilent.com
Alexander Neundorf said the following on 2/6/2012 3:56 PM:
Would it be acceptable if cmake would rerun after every build ?
You could enforce that e.g. with a add_custom_command( POST_BUILD ... ) which
could e.g. touch CMakeCache.txt or something.
Better ideas ?
We're working in a client/server
Michael Hertling said the following on 2/6/2012 6:39 PM:
On 02/06/2012 10:56 PM, Alexander Neundorf wrote:
On Saturday 04 February 2012, Oliver Smith wrote:
My CMakeLists uses the Subversion repository information in a couple of
places (it configures a file revision.h and it uses it for the
I think this could work, but if compiler is altered before project() call
(but I didn't check this and suggest set variable only if it's not already
set). Specifying only one variable in command line looks more
user-friendly and robust than several ones.
Anther option is using initial cache.
I use a special macro for such purposes, something like this:
Sub Install()
Dim prj As Project
Dim sb As SolutionBuild = DTE.Solution.SolutionBuild
Dim prjs As Projects = DTE.Solution.Projects
For Each prj In prjs
If prj.Name = INSTALL Then
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 85138471659200d3650ea7b7d0a000ce1c873755 (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 deb696247fb4a48477ed100e5ddd49f8d13e2400 (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 319ec8fe8e53b480fe6400d83887bbaee2f89695 (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 32410b69501825b539ced3bc3640a60eb75d6cef (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 cb4ed0b7994a04f82c14f48edb6c2c7bb2f6a046 (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 7c20788c16f5092060d27c3d7741f8685d67ded9 (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 e36cce123f4e5449fe6f8bfa22d5f3881d94e533 (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 267cc72af16065a85f935d6e046d6cf8a604fc28 (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 16b1a6e4e07b223c7ead20cd40346fc327e90569 (commit)
from
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 64dc9710d533f076b2f1cfe3201beba5e0998e64 (commit)
via
32 matches
Mail list logo
