mirror of
https://github.com/Kitware/CMake.git
synced 2026-05-06 14:19:59 -05:00
572994bd9f
8485208Ninja: shell escape $(CMAKE_SOURCE_DIR) and $(CMAKE_BINARY_DIR)df84767Ninja: add support for OBJECT_OUTPUTS, fix PrecompiledHeader test case48eb7fcNinja: Avoid using 'this' in member initializersbba37ddNinja: Fix for PDB files with spaces in the path.ac800f4Ninja: Constify use of cmCustomCommand9a0d5a8Ninja: add /DEF: flag to linker calld40eebdNinja: Add a cache option CMAKE_ENABLE_NINJA to enable the ninja generator.8c63433Ninja: Add friend struct so it can access the private ConvertToNinjaPath.dbe3dceNinja: add .def file supportf1bb08fNinja: ensure the output dir exists at compile time7a6b5f4Ninja: Remove an unnecessary variable80ff210Ninja: Use cmSystemTools::ExpandListArgument to split compile/link commandsd2731a3Ninja: Add a missed license headereabc9b0Ninja: CMake: Adapt Ninja generator for per-target include dirsbada88eMerge branch 'target-include-directories' into ninja-generator54bd175Ninja: windows msvc: create for each target a .pdb file ...
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.