_________________________________________________________
Mike Jackson mike.jack...@bluequartz.net
BlueQuartz Software www.bluequartz.net
Principal Software Engineer Dayton, Ohio
On May 18, 2009, at 11:19 AM, Brad King wrote:
troy d. straszheim wrote:
I've had a fair amount of difficulty getting ctest scripts to work.
The best I've been able to come up with is
1. Configure a build space with cmake -DBUILD_REGRESSION_TESTS=ON
1a. Customize as necessary
2. Run ctest -D Whatever
I've played with having cmake try to configure_file() a ctest
script into the CMAKE_BINARY_DIR if BUILD_REGRESSION_TESTS is ON,
but this has been problematic. What is the recommended approach?
The script can be written totally outside the source and build trees.
If written properly it can do the initial checkout and create the
build
tree. A standalone script I use to do one of CMake's builds appears
below.
You can also create project-specific helper scripts like this one:
https://vxl.svn.sourceforge.net/svnroot/vxl/trunk/config/cmake/ctest-scripts/
http://vxl.sourceforge.net/submit-build.html
This makes the individual contributor scripts very small.
-Brad
Brad,
thanks for the heads up about vxl. I took those 2 scripts and
adapted them for boost. I have since been able to submit an
experimental Dashboard to <http://www.cdash.org/CDashPublic/index.php?project=Boost
>. Look for f...@bluequartz.net - the one that actually ran all the
tests.
Also, if you click on the "site" you get some stats about the machine
that built boost.. All of which is either wrong or not filled in. Are
there some configuration options for this that need to be set or is
the parsing code for CTest not grepping OS X machines correctly?
Thanks for the help with this
Mike Jackson
_______________________________________________
Boost-cmake mailing list
Boost-cmake@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
