Changes between Version 1 and Version 2 of CMakeTesting


Ignore:
Timestamp:
Jun 12, 2007, 8:11:59 PM (15 years ago)
Author:
troy d. straszheim
Comment:

factor out explanations of how to run ccmake into separate page

Legend:

Unmodified
Added
Removed
Modified

  • CMakeTesting

    v1 v2  
    11= Testing Boost with CMake =
    2 Boost's CMake-based build system provides regression testing via [http://www.cmake.org/Wiki/CMake_Testing_With_CTest CTest], which comes as part of CMake. This regression testing system can be used by Boost developers to test their libraries locally and also by testers and users to submit regression tests to a [http://public.kitware.com/Dart Dart server], which collects and reports regression-testing results from different sites. This document assumes that the reader has already learned how to [http://svn.boost.org/trac/boost/wiki/CMakeConfigAndBuild configure and build] Boost using CMake.
     2Boost's CMake-based build system provides regression testing via [http://www.cmake.org/Wiki/CMake_Testing_With_CTest CTest], which comes as part of CMake. This regression testing system can be used by Boost developers to test their libraries locally and also by testers and users to submit regression tests to a [http://public.kitware.com/Dart Dart server], which collects and reports regression-testing results from different sites. This document assumes that the reader has already learned how to [wiki:CMakeConfigAndBuild build] and [wiki:CMakeBuildConfiguration configure] Boost using CMake.
    33
    4   1. Re-run the CMake configuration for Boost, either by running the CMake configuration program from the Start menu (on Microsoft Windows) or executing the command-line CMake configuration in Unix:
    5   {{{
    6 ccmake $BOOST_ROOT
    7   }}}
     4  * Re-run the [wiki:CMakeBuildConfiguration CMake configuration for Boost].  Set `BUILD_TESTING` to `ON`. You may notice that configuration takes significantly longer when we are building all of the regression tests.  If you want you can disable regression testing for some or all Boost libraries by toggling the `TEST_BOOST_`''libname'' options that appear once `BUILD_TESTING` is `ON`. Be sure to re-configure CMake once you are done tweaking these options, and generate makefiles or project files, by clicking "OK" (on Microsoft Windows) or pressing `g` (on Unix).
    85
    9   2. Toggle the `BUILD_TESTING` option in the CMake configuration to `ON`, and then re-configure (either by clicking "Configure", on Microsoft Windows, or pressing `c`, on Unix). You may notice that configuration takes significantly longer when we are building all of the regression tests.
    10 
    11   3. If you want, you can now disable regression testing for some or all Boost libraries by toggling the `TEST_BOOST_LIBNAME` options that appear. Be sure to re-configure CMake once you are done tweaking these options.
    12 
    13   4. Generate makefiles or project files, by clicking "OK" (on Microsoft Windows) or pressing `g` (on Unix).
    14 
    15   5. Follow the same building process described in the section [http://svn.boost.org/trac/boost/wiki/CMakeConfigAndBuild Configuring and Building Boost], either be running your make program from the Boost binary directory or compiling from within your IDE (e.g., Microsoft Visual Studio). For Unix users, we suggest passing the `-i` option to `make`, and also possibly `-j 2` (or more) to run the build process in parallel. Building all of the regression tests for the Boost libraries can take a long time.
    16   {{{
     6  * Build, following the same building process described in the section [wiki:CMakeConfigAndBuild].  For Unix users, we suggest passing the `-i` option to `make`, and also possibly `-j 2` (or more) to run the build process in parallel. Building all of the regression tests for the Boost libraries can take a long time.
     7{{{
    178make -i -j 2
    18   }}}
     9}}}
    1910 
    2011  '''Note''': If you change Boost source files in a way that affects your tests, you will need to re-run the build process to update the libraries and tests before moving on to the next step.
    2112
    22   6. Once regression tests have finished building, go into the command line or command prompt and enter the Boost binary directory. Then, run the command
     13  * Once regression tests have finished building, go into the command line or command prompt and enter the Boost binary directory. Then, run the command
    2314  {{{
    2415ctest
    … …  
    5546  }}}
    5647
    57   Here, we have only enabled testing of the Boost.Any and Boost.Function libraries, by setting `TEST_BOOST_ANY` and `TEST_BOOST_FUNCTION` to `ON` while all of the other `TEST_BOOST_LIBNAME` options are set to `OFF`.
     48  Here, we have only enabled testing of the Boost.Any and Boost.Function libraries, by setting `TEST_BOOST_ANY` and `TEST_BOOST_FUNCTION` to `ON` while all of the other `TEST_BOOST_`''LIBNAME'' options are set to `OFF`.
     49
     50  '''Again''':  This "`ctest`" step runs the tests without first running a build.  If you change a source file and run the `ctest` step you will see that no build is invoked. 
    5851
    5952== Submitting Regression Test Results ==