mirror of
https://github.com/Kitware/CMake.git
synced 2026-01-04 21:00:17 -06:00
ce167b54cmMakefile: Handle CMP0014 before configuring the generator.7baef756cmLocalGenerator: Assert that there is a parent.63255342cmMakefile: Remove redundant variable set.894961afcmMakefile: Use the state to determine the parent directory.115e9199Use new top-level check abstraction.c5059c90cmLocalGenerator: Add abstraction to check if top-level.b17686d2cmGlobalGenerator: Move some flags from cmLocalGenerator.ed41a8e7cmLocalGenerator: Port loops to cmState::Snapshot.48a9e91bcmState: Add an accessor for Parent snapshot and a validity check.e7f7c2e2cmLocalGenerator: Convert two recursive methods to loops.c5cb3a73cmLocalGenerator: Get project directories from the cmState.76b59831cmLocalGenerator: Initialize state before creating cmMakefile.34c9ee2ecmLocalGenerator: Require a global generator in the constructor.3837c483Tests: Add case for 'ctest' run with bad CTestTestfileb317b38dcmGlobalBorlandMakefileGenerator: Do not inherit from NMake generator94867698Don't use a cmLocalGenerator instance to call static methods. ...
If you think about adding a new testcase then here is a small checklist you can run through to find a proper place for it. Go through the list from the beginning and stop once you find something that matches your tests needs, i.e. if you will test a module and only need the configure mode use the instructions from section 2, not 3. 1. Your testcase can run in CMake script mode, i.e. "cmake -P something" Put your test in Tests/CMakeTests/ directory as a .cmake.in file. It will be put into the test binary directory by configure_file(... @ONLY) and run from there. Use the AddCMakeTest() macro in Tests/CMakeTests/CMakeLists.txt to add your test to the test runs. 2. Your test needs CMake to run in configure mode, but will not build anything This includes tests that will build something using try_compile() and friends, but nothing that expects add_executable(), add_library(), or add_test() to run. If the test configures the project only once and it must succeed then put it into the Tests/CMakeOnly/ directory. Create a subdirectory named like your test and write the CMakeLists.txt you need into that subdirectory. Use the add_CMakeOnly_test() macro from Tests/CMakeOnly/CMakeLists.txt to add your test to the test runs. If the test configures the project with multiple variations and verifies success or failure each time then put it into the Tests/RunCMake/ directory. Read the instructions in Tests/RunCMake/CMakeLists.txt to add a test. 3. If you are testing something from the Modules directory Put your test in the Tests/Modules/ directory. Create a subdirectory there named after your test. Use the ADD_TEST_MACRO macro from Tests/CMakeLists.txt to add your test to the test run. If you have put your stuff in Tests/Modules/Foo then you call it using ADD_TEST_MACRO(Module.Foo Foo). 4. You are doing other stuff. Find a good place ;) In doubt mail to cmake-developers@cmake.org and ask for advise.