ces of information, but it may
help. It does have the benefit of putting this information in a very visible
spot on the dashboard.
You can also set CTEST_BUILD_NAME to hold a couple other pieces of data. I
use that to specify which build flags were used and which subset of tests
was run.
Ceej
aka
ouldn't have to, unless you're using in-source builds which is
very strongly deprecated. Once you've gotten used to out-of-source builds
you'll never want to go back. Read section 3 of the FAQ about out-of-source
builds.
Good luck,
Ceej
aka Chris Hillery
here? Your
add_custom_command() and list(APPEND SRCS) steps below will do this if you
just change the OUTPUT to "${CMAKE_CURRENT_BINARY_DIR}/SourceFileInfo.cpp".
This would have the added benefit of not forcing a rebuild of
SourceFileInfo.o every time you run "make".
Ceej
aka Chris H
ed out if
this is a flaw with our scheme, with VS2010, or with CMake's VS2010
generator, although our current bet is on CMake - certainly there have been
other reports of difficulties with custom commands in VS2010. If you're
coming from a strictly Makefile-based project, this probably won't ma
well.
Ceej
aka Chris Hillery
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
e the same is true of Perforce and probably other systems.
Ceej
aka Chris Hillery
On Wed, Sep 15, 2010 at 1:40 AM, Olivier Pierard wrote:
> Dear all,
>
> For several testcases validations, I use 'cmake -E compare_files'
> command on a result file against a reference file. Pr
CUTE_PROCESS (COMMAND /my/custom/envprogram)
and expecting envprogram to be able to modify your environment, however,
that won't work for the reasons Gerhard and I said - the command is
executing in a subshell, and by definition a subshell cannot affect the
enviro
irmed that the variable was set in the environment for both
the ctest_configure and ctest_build steps.
Can you reduce this to a small example, maybe?
Ceej
aka Chris Hillery
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
h
nse as a read-only directory property ?
>
As long as you can iterate over directories too! :)
Ceej
aka Chris Hillery
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please ke
t you wouldn't have to modify any sub-project build
files. Just
function (add_library name )
# do stuff to remember this target
_add_library (name )
endfunction (add_library)
Not 100% ideal, but a relatively small amount of work should get you what
y
way
from within my overwritten forms to call the original, so it's not very
useful.)
Ceej
aka Chris Hillery
On Sun, Sep 5, 2010 at 3:51 PM, Clifford Yapp wrote:
> Is there any way within a CMakeLists.txt file to get a list of all the
> currently defined targets? I'm interested in
which attempted to be a "better Make"
which is effectively what you're describing. There's nothing wrong with
that, but that isn't what CMake does. If that's what you want in a tool,
then I think you'll be happier finding a tool with that goal - always pick
the right
n't what CMake does. If that's what you want in a tool,
then I think you'll be happier finding a tool with that goal - always pick
the right tool for the job at hand!
Ceej
aka Chris Hillery
___
Powered by www.kitware.com
Visit other Kitwa
bly code for several major
platforms, and then you could store the generated assembly files in version
control..."
Ceej
aka Chris Hillery
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/open
Check out this article:
http://www.kitware.com/blog/home/post/11
and read the article in the Kitware Quarterly that is linked to from there
on "CDash subprojects".
It's not nearly as clean and straightforward as it should be, IMHO, but it
does work.
Ceej
aka Chris Hillery
On Tu
OURCE_DIR}
)
You'll need to tweak the invocation of addtestscript to successfully
generate testlist.cmake in the build directory, and then I think it'll all
work.
Ceej
aka Chris Hillery
___
Powered by www.kitware.com
Visit other Kitware open-sou
ty ctest and cdash offer. (To be fair, even if this were fixed in
ctest, CxxTest would also need some modifications as it currently doesn't
let you run subsets of tests either.)
Ceej
aka Chris Hillery
On Fri, Jul 9, 2010 at 4:37 AM, Bo Thorsen wrote:
> Hi people,
>
> I have converte
On Wed, Jul 7, 2010 at 12:32 AM, Michael Hertling wrote:
> IMO, things aren't sooo bad. ;-)
>
> [100 lines of explanation of how SET() behaves in 6 different ways elided]
>
I think you've just proven my point. Thanks! :)
. Maybe it would be possible to change it such that a cache variable
declaration (option() or set(...CACHE...) ) would allow a current non-cache
variable of the same name to override the declaration's default value, in
the same way that -D on the command-line does.
Ceej
aka Chris Hillery
On F
7;if(VAR)'. That will be true as long as VAR is not undefined, 0, "", N, NO,
OFF, FALSE, NOTFOUND, or -NOTFOUND.
If you really need to only match empty string, then probably 'if(VAR
STREQUAL "")' would be a little easier to read and type.
Ceej
aka Chris Hillery
__
Try this:
ctest -T Test
This will generate the same Test.xml logfile as running ctest -D, but it
won't do all the other dashboard steps (update, configure, build...).
Ceej
aka Chris Hillery
On Wed, Jun 30, 2010 at 3:46 AM, David Cole wrote:
> On Wed, Jun 30, 2010 at 6:22 AM, David Co
d changing away from
global variables or at least having a massive rename-fest would be difficult
to achieve with anything like compatibility. Perhaps CMake 3.0 could have a
clean break...
Ceej
aka Chris Hillery
On Sun, Jun 27, 2010 at 1:52 PM, Convey, Christian J CIV NUWC NWPT <
christian.con...
I don't think the CMake list is the place to ask this question, as it sounds
like a problem with OTB. At the very least I would ask for help first with
the developers of OTB.
Also, I would suggest when asking them, that you include the actual error
messages that you saw.
Ceej
aka Chris Hi
e, clearly it is meant to support a
"Nightly" dashboard. However, experimentally, I've determined that it takes
effect if it is set no matter what type of dashboard you're running.
Ceej
aka Chris Hillery
On Thu, Jun 24, 2010 at 6:03 AM, Convey, Christian J CIV NUWC NWPT <
christi
do what the URL lists, though, you
might get what you want.
> I'd like to continue specifying my tests by having "ADD_TEST(...)" calls
> sprinkled throughout my project's CMakeLists.txt files.
>
Yes, please; don't ever stop doing that. It's just
covers thus unfortunately grows ever taller.
But, back to the original subject, if you can re-state what your goal is a
little bit, hopefully we can figure out a way to get you there.
Ceej
aka Chris Hillery
___
Powered by www.kitware.com
Visit other Kitw
script" is
that it uses the functions ctest_start(), ctest_configure(), etc.
Anyway, that was probably a lot more than you wanted to know at this time,
but hopefully it will serve some value in future. Meanwhile, I suspect
there's probably a straightforward way to do what you actually wa
...), it's set (CTEST_BUILD_TARGET ...) and then
ctest_build() will build that.
Ceej
aka Chris Hillery
On Mon, Jun 14, 2010 at 9:58 AM, wrote:
> Hi there,
>
> I reported a bug a couple of month back, which apparently was fixed with
> "Closing this since the new TARGET option fo
t;
>
FYI:
http://www.cmake.org/Wiki/CMake_FAQ
Question 2.1. There's a lot of other good stuff in there too! :)
Ceej
aka Chris Hillery
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensour
er of tests had been run, and let it
populate and submit the XML report based on that information. But, if
there's any way to do that, it's highly undocumented...
Ceej
aka Chris Hillery
___
Powered by www.kitware.com
Visit other Kitware open-s
rate CDash-compatible XML
output from my testdriver? And how would I go about uploading those results?
Ceej
aka Chris Hillery
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Ple
Would it be possible to use ctest -D without actually submitting to CDash?
Something like
ctest -D ExperimentalCoverage
seems like it would do the same thing that nightlies do, just for a single
local build without submitting the results.
Ceej
aka Chris Hillery
On Mon, Jun 7, 2010 at 6:36 PM
x27;m afraid I
have not yet been able to test this out with CMake 2.8. I don't know if
Kitware does maintenance releases for previous revisions.
Ceej
aka Chris Hillery
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://
;m not sure if ctest will
look at stderr at all.)
Also, might something else in your CMakeLists.txt be overriding the
tests_properties for test4?
Ceej
aka Chris Hillery
On Sun, Feb 7, 2010 at 6:59 AM, AlannY wrote:
> Hi there. I'm trying to write some tests for my library with CTest.
thing!
So, tell me - are there any other features for generically modifying file
permissions without copying the file?
Ceej
aka Chris Hillery
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/openso
Whoops - I take it back. I see that it IS there in the 2.8 online docs, as a
separate file( entry as you said. Not terribly clear IMHO, but
anyway. So I guess this is a new 2.8 feature (it really truly isn't there in
2.6.4).
Ceej
aka Chris Hillery
On Wed, Feb 3, 2010 at 3:04 AM, Chris Hi
n't want to muck with a configured
file after configuring it. However, I expect there are some non-ideal
situations which might require that, so the above work-around should get you
going.
Ceej
aka Chris Hillery
___
Powered by www.kitware.com
Visit o
e same is true for the free Visual Studio Express (which somewhat
confusingly is NOT identified as "the free VC compiler" by CMake, but it all
works fine).
Ceej
aka Chris Hillery
___
Powered by www.kitware.com
Visit other Kitware o
38 matches
Mail list logo