CMake:如何使用相关目录添加 Boost.Test 用例?

2021-12-24 00:00:00 cmake c++ boost ctest boost-test

我有一个使用 CMake 和 Boost.Test 的工作项目，其目录结构如下(请原谅 ASCII 艺术):

I have a working project with CMake and Boost.Test with a directory structure like this (pardon the ASCII art):

+-proj |---CMakeLists.txt |---build |---test |----dir1 | ----foo.cpp // contains one BOOST_AUTO_TEST_SUITE and several BOOST_AUTO_TEST_CASE | |---bar.cpp // contains one BOOST_AUTO_TEST_SUITE and several BOOST_AUTO_TEST_CASE ----dir2 ----foo.cpp // contains one BOOST_AUTO_TEST_SUITE and several BOOST_AUTO_TEST_CASE |---bar.cpp // contains one BOOST_AUTO_TEST_SUITE and several BOOST_AUTO_TEST_CASE

我目前将所有源文件编译成一个可以使用 CTest 运行的大型可执行文件.我的 CMakeLists.txt 看起来像这样:

I currently compile all source files into one big executable that I can run with CTest. My CMakeLists.txt looks like this:

file(GLOB_RECURSE test_cases FOLLOW_SYMLINKS "test/*.[h,c]pp") add_executable(test_suite ${test_cases}) include_directories(${PROJECT_SOURCE_DIR} ${Boost_INCLUDE_DIRS}) target_link_libraries(test_suite ${Boost_LIBRARIES}) include(CTest) add_test(test_runner test_suite)

我想将每个 .cpp 文件编译成一个单独的可执行文件，并将其单独添加为测试，以便我可以使用 CTest 正则表达式机制(尤其是 Boost.Test 似乎没有的测试排除)有选择地运行某些测试.但是，当 CMake 从 dir1/dir2 为 foo/bar 生成构建目标时，我遇到了名称冲突.

I would like to compile each .cpp file into a separate executable, and add it separately as a test so that I can use the CTest regular expression machinery (especially the test exclusion which Boost.Test doesn't seem to have) to selectively run certain tests. However, I get a name conflict when CMake is generating build targets for foo/bar from dir1/dir2.

我的问题是:如何将 test 下的整个目录树镜像到 build 下的类似树，以便不再有各种可执行文件之间的名称冲突，以便 CTest 可以运行它们?

My question is: how can I mirror the entire directory tree under test to a similar tree under build so that there are no more name conflicts between the various executables and so that CTest can run them all?

注意:不能在源代码树中重命名它们.我想对变量 ${test_cases} 执行 foreach() (如这个答案)，但我无法提取相关目录和文件名，并将它们移植到文件一个文件的 build/ 目录中基础.

Note: Renaming them in the source tree is not an option. I'd like to do a foreach() over the variable ${test_cases} (as explained in this answer), but I am having trouble to extract the relative directory and the file name, and port those to the build/ directory on a file-by-file basis.

UPDATE:最后，我拼凑了这个脚本:

UPDATE: In the end, I pieced together this script:

# get the test sources file(GLOB_RECURSE test_sources RELATIVE ${PROJECT_SOURCE_DIR} *.cpp) # except any CMake generated sources under build/ string(REGEX REPLACE "build/[^;]+;?" "" test_sources "${test_sources}") # get the test headers file(GLOB_RECURSE test_headers RELATIVE ${PROJECT_SOURCE_DIR} *.hpp) # except any CMake generated headers under build/ string(REGEX REPLACE "build/[^;]+;?" "" test_headers "${test_headers}") # compile against the test headers, the parent project, and the Boost libraries include_directories(${PROJECT_SOURCE_DIR} ${ParentProject_include_dirs} ${Boost_INCLUDE_DIRS}) # calls enable_testing() include(CTest) foreach(t ${test_sources} ) # get the relative path in the source tree get_filename_component(test_path ${t} PATH) # get the source name without extension get_filename_component(test_name ${t} NAME_WE) # concatenate the relative path and name in an underscore separated identifier string(REPLACE "/" "_" test_concat "${test_path}/${test_name}") # strip the leading "test_" part from the test ID string(REGEX REPLACE "^test_" "" test_id ${test_concat}) # depend on the current source file, all the test headers, and the parent project headers add_executable(${test_id} ${t} ${test_headers} ${ParentProject_headers}) # link against the Boost libraries target_link_libraries(${test_id} ${Boost_LIBRARIES}) # match the relative path in the build tree with the corresponding one in the source tree set_target_properties(${test_id} PROPERTIES RUNTIME_OUTPUT_DIRECTORY ${test_path}) # add a test with executable in the relative path of the build tree add_test(${test_id} ${test_path}/${test_id}) endforeach()

推荐答案

可以指定 RELATIVE 标志和文件的目录( GLOB ... ) 命令.虽然在文件(GLOB)文档中没有直接提到a>，这也适用于 file( GLOB_RECURSE ... ) .请注意，我在 Windows 设置中对此进行了测试.我不知道 *nix.

It is possible to specify a RELATIVE flag and a directory to a file( GLOB ... ) command. Although not mentioned directly in the documentation of file( GLOB ), this works for file( GLOB_RECURSE ... ) too. Note, I tested this on my windows setup. I don't known about *nix.

连同一些 get_filename_component 调用与 <代码>NAME_WE和/或 PATH 标志，现在可以重建名称和cpp 文件相对于 globbing 目录的相对路径.
提取路径和名称(不带扩展名)大多类似马西米利亚诺的回答.另外，我用过他的建议使用 string( REGEX REPLACE ... ) 生成唯一的测试名称；用下划线替换正斜杠.
使用唯一的测试名称，可以生成可执行文件，然后可以使用 set_target_properties.

Together with some get_filename_component calls with NAME_WE and/or PATH flags, it is now possible to reconstruct the name and the relative path of the cpp-file with respect to the globbing dir.

Extracting a path and a name (without extension) is mostly similar to the answer by Massimiliano. In addition, I have used his suggestion to generate a unique testname with string( REGEX REPLACE ... ); replacing forward slashes by underscores.

With a unique test-name, the executable can be generated and afterwards its output directory can be modified with set_target_properties.

检查这个和这个问题有关修改输出目录的更多信息.

Check this and this question for more info on modifying the output directory.

file( GLOB_RECURSE TEST_CPP_SOURCES RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} *.cpp ) foreach( test_case ${TEST_CPP_SOURCES} ) # Get the name without extension get_filename_component( test_name ${test_case} NAME_WE ) # Get the path to the test-case, relative to the ${CMAKE_CURRENT_SOURCE_DIR} # thanks to the RELATIVE flag in file( GLOB_RECURSE ... ) get_filename_component( test_path ${test_case} PATH ) message( STATUS " name = " ${test_name} ) message( STATUS " path = " ${test_path} ) # I would suggests constructing a 'unique' test-name string( REPLACE "/" "_" full_testcase "${test_name}/${test_path}" ) # Add an executable using the 'unique' test-name message( STATUS " added " ${full_testcase} " in " ${test_path} ) add_executable( ${full_testcase} ${test_case} ) # and modify its output paths. set_target_properties( ${full_testcase} PROPERTIES RUNTIME_OUTPUT_DIRECTORY ${test_path} ) endforeach( test_case ${TEST_CPP_SOURCES} )

相关文章