Hi!
I am currently working on a project which uses plain old make as a build
system. Needless to say, adding new compilers etc. is a lot of work, so I would
like to start using CMake, which I have had excellent experience with in the
past.
There is one peculiarity that I do not know how to han
Apologies if this is a stupid question with an obvious answer staring me in the
face but...
How does one view the full build log from the dashboard? This relates to our
own dashboard but looking at a build of CMake as an example
(http://open.cdash.org/buildSummary.php?buildid=3450103) The full
I found a workaround. Turns out that the issue is caused when not enabling C
language support in the project() command. i.e I was doing
cmake_minimum_required( VERSION 3.0.0 )
project( proj CXX)
Changing this to
cmake_minimum_required( VERSION 3.0.0 )
project( proj CXX)
fixes t
In my opinion this is a deficiency in how cmake currently works with object
libraries. If one of the source files in an object library depends on a
third library then it should be possible to specify that in the link
interface of either the object library or the source file. It is wrong to
have t
On 8/14/2014 11:26 AM, Nagger wrote:
So ZERO_CHECK is 34 times faster. Why shouldn't I take advantage of that.
If CMake does not need to re-run, then ZERO_CHECK will always be faster
than cmake build_dir. cmake build_dir will run a full configure and
generate no matter what. That said, a cm
Am 14.08.2014 16:31, schrieb David Cole:
We have a fairly large project with about 400 targets.
$ cmake %builddir%
-> takes about 5 minutes for a No-op
$ cmake --build %builddir% --target ZERO_CHECK
-> takes 20 seconds for No-op
This is the problem.
"cmake %builddir%" should be as fas
We have a fairly large project with about 400 targets.
$ cmake %builddir%
-> takes about 5 minutes for a No-op
$ cmake --build %builddir% --target ZERO_CHECK
-> takes 20 seconds for No-op
This is the problem.
"cmake %builddir%" should be as fast as possible for a no-op... If it's
not,
Am 14.08.2014 08:13, schrieb Hendrik Sattler:
On 13. August 2014 21:40:34 MESZ, Nagger wrote:
But what I really miss is an "--update" option for CMake which is doing
all the work (updating if possible, configuring if necessary)
internally. It would use the implementation of 'cmake --build' to
OK, thanks for the informations. It's a lot more clear now.
YC
- Mail original -
De: "David Cole"
À: "ycollette nospam" , cmake@cmake.org
Envoyé: Jeudi 14 Août 2014 13:33:01
Objet: Re: [CMake] ctest and tracks
--track is the same as the TRACK argument to the ctest_start scripting
comma
A "SET(ENV{TARGET2_EXE_PATH} "C:/Test/Target2")" call in a CMakeLists
file only has an effect while CMake is running.
If you need the env var set for your batch file to run, you should pass
the value for it down in as an arg to the batch file, and then do:
set TARGET2_EXE_PATH=%~1
(no quo
Hi David,
In our cmake project, we have the following scenario:
1. add_custom_command() call is as follows:
add_custom_command(TARGET ${TESTTARGETNAME}
POST_BUILD
--track is the same as the TRACK argument to the ctest_start scripting
command.
http://www.cmake.org/cmake/help/v3.0/command/ctest_start.html
It will send a dashboard to the named section of a CDash project page,
but it will NOT create it. You have to create the track (called a
"group" in
Hello,
I've have configured a project to use dash to save test results.
On thing is not clear in the ctest documentation: what is the use of the
--track option ? Does it allow to create a new category (like Weekly) and
submit the test results to this new category ?
Best regards,
YC
--
Powere
13 matches
Mail list logo
