mirror of
https://github.com/Kitware/CMake.git
synced 2026-01-19 04:59:48 -06:00
bb9d71b4Replace loops with algorithms.4afe6c26cmAlgorithms: Add cmReverseRange adaptor.a3a0a8c2cmAlgorithms: Add cmFindNot algorithm.8c74a41fcmRST: Replace two erase with a rotate and larger erase.61fe1919cmAlgorithms: Update concept requirement to FowardIterator09d6125bcmAlgorithms: Move cmRotate out of 'implementation detail' namespace.8ed6ecaccmRST: Move two algorithms beside each other.dfe49c20cmRST: Use std::min where appropriate.21b0654acmGlobalGenerator: Convert set insert algorithm to vector algorithms.416df93aConvert some raw loops to cmWrap.37b88d34cmAlgorithms: Add cmWrap.a2818093Use cmJoin where possible.76207b08cmCacheManager: Replace loop with algorithm.60c3bb73cmGlobalGenerator: Replace loop with algorithm.05fec779cmTarget: Port loop to algorithm.9c225767cmGlobalGenerator: Replace set::insert algorithm with cmRemoveDuplicates. ...
This directory contains tests that run CMake to configure a project
but do not actually build anything. To add a test:
1. Add a subdirectory named for the test, say ``<Test>/``.
2. In ``./CMakeLists.txt`` call ``add_RunCMake_test`` and pass the
test directory name ``<Test>``.
3. Create script ``<Test>/RunCMakeTest.cmake`` in the directory containing::
include(RunCMake)
run_cmake(SubTest1)
...
run_cmake(SubTestN)
where ``SubTest1`` through ``SubTestN`` are sub-test names each
corresponding to an independent CMake run and project configuration.
One may also add calls of the form::
run_cmake_command(SubTestI ${CMAKE_COMMAND} ...)
to fully customize the test case command-line.
4. Create file ``<Test>/CMakeLists.txt`` in the directory containing::
cmake_minimum_required(...)
project(${RunCMake_TEST} NONE) # or languages needed
include(${RunCMake_TEST}.cmake)
where ``${RunCMake_TEST}`` is literal. A value for ``RunCMake_TEST``
will be passed to CMake by the ``run_cmake`` macro when running each
sub-test.
5. Create a ``<Test>/<SubTest>.cmake`` file for each sub-test named
above containing the actual test code. Optionally create files
containing expected test results:
``<SubTest>-result.txt``
Process result expected if not "0"
``<SubTest>-stdout.txt``
Regex matching expected stdout content
``<SubTest>-stderr.txt``
Regex matching expected stderr content, if not "^$"
``<SubTest>-check.cmake``
Custom result check.
Note that trailing newlines will be stripped from actual and expected
test output before matching against the stdout and stderr expressions.
The code in ``<SubTest>-check.cmake`` may use variables
``RunCMake_TEST_SOURCE_DIR``
Top of test source tree
``RunCMake_TEST_BINARY_DIR``
Top of test binary tree
and an failure must store a message in ``RunCMake_TEST_FAILED``.