Hi David,
Thanks for your quick reply. I understand that it makes sense for the make
Experimental to skip the update step. Do you then mean to run something like
ctest -D ExperimentalStart \
-D ExperimentalUpdate \
-D ExperimentalBuild \
-D ExperimentalConfigure\
-D ExperimentalTest \
-D ExperimentalSubmit
?
I tried to write a script which had the following content:
set(CTEST_SOURCE_DIRECTORY "/path/to/source/")
set(CTEST_BINARY_DIRECTORY "${CTEST_SOURCE_DIRECTORY}/build")
set(CTEST_CMAKE_GENERATOR "Unix Makefiles")
set(CTEST_UPDATE_COMMAND "svn")
ctest_empty_binary_directory(${CTEST_BINARY_DIRECTORY})
ctest_start(Experimental)
ctest_update()
ctest_configure()
ctest_build()
ctest_test()
ctest_submit()
That seemed to work as expected, but then on the cdash web page, I had four
separate submissions (one for each of update, configure, build, and testing),
and none
of them had a site name. I guess I could set the CTEST_BUILD_NAME to get that
working. I also did not get the initial cmake command output included. I would
still think at the moment it is better with the "make Experimental" than this
solution as it stands for me now.
Perhaps a simple shell script is the best way to go? That is what I am doing at
the moment and it is not hugely important for me to have the update column
populated. I am actually more curious about getting the full output from the
initial cmake configuration included in the report.
Cheers,
Yngve
Onsdag 15 juni 2011 12.37.10 skrev David Cole :
> "make Experimental" intentionally skips the update step. If you want to do
> the same thing as "make Experimental" but add the update step, you'll have
> to run ctest with appropriate -D or -M and -T arguments, or write a ctest -S
> script to do the steps you'd like to do.
>
>
> HTH,
> David
>
>
> On Wed, Jun 15, 2011 at 6:03 AM, Yngve Inntjore Levinsen <
> yngve.levin...@gmail.com> wrote:
>
> > Dear developers,
> >
> >
> > I am sure this has been answered before, but I cannot find the information.
> > I apologize in advance for my ignorance.
> >
> >
> > I have set up our project with cmake/ctest, and have a cdash server
> > running. I have configured everything so that if I run in the source
> > directory
> >
> >
> > mkdir build;cd build;cmake ..;make Experimental
> >
> >
> > then I get a submitted report in the Experimental category on the cdash
> > server. Now, what I note here is that I do not get the configuration part
> > included as a part of the report (it does run cmake a second time, but that
> > only runs the "update part"), and I do not get the svn update (?). What I am
> > looking for is a simple script that includes those two as well. In principle
> > it should just need to explain ctest where the svn repository path is, and
> > then tell it to run cmake+make+ctest for that project in a specified
> > temporary folder. Everything else is set up in CMakeLists.txt and
> > CTestConfig.cmake (including information about cdash server location++). The
> > examples I've come across have been significantly more complex and I am a
> > bit confused about what should be configured where clearly.
> >
> >
> > Thank you very much for your help!
> >
> >
> > Best Regards,
> >
> > Yngve I. Levinsen
> >
> > _______________________________________________
> > 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
> >
> > Follow this link to subscribe/unsubscribe:
> > http://www.cmake.org/mailman/listinfo/cmake
> >
>
_______________________________________________
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
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
