Catch2 测试宏与平台头文件命名冲突时如何用前缀宏解决【免费下载链接】Catch2A modern, C-native, test framework for unit-tests, TDD and BDD - using C14, C17 and later (C11 support is in v2.x branch, and C03 on the Catch1.x branch)项目地址: https://gitcode.com/GitHub_Trending/ca/Catch2如果你在用 Catch2 写测试时编译报错指向TEST_CASE、REQUIRE这类短宏名而报错源头是某个平台头文件或被测试代码里恰好定义了同名宏问题通常出在 Catch2 的用户宏与外部标识符撞名。Catch2 的官方做法是定义CATCH_CONFIG_PREFIX_ALL让所有 Catch 用户宏加上CATCH_前缀例如CATCH_TEST_CASE、CATCH_REQUIRE或者定义CATCH_CONFIG_PREFIX_MESSAGES只给消息宏加前缀。这篇文章说明怎么选、怎么定义以及如何验证前缀确实生效。什么情况下会冲突以及两个前缀宏的适用范围docs/configuration.md 在 “Prefixing Catch macros” 一节解释了背景为了保持测试代码干净Catch 使用短宏名如TEST_CASE和REQUIRE。文档原话是这些短名偶尔会与平台头文件或被测试系统system under test中的标识符冲突此时定义下面两个宏之一即可CATCH_CONFIG_PREFIX_ALL // Prefix all macros with CATCH_ CATCH_CONFIG_PREFIX_MESSAGES // Prefix only message macros ((UNSCOPED_)INFO, WARN, (UNSCOPED_)CAPTURE)选择标准按冲突面大小来冲突涉及TEST_CASE、REQUIRE等通用测试宏时用CATCH_CONFIG_PREFIX_ALL它让所有Catch 用户宏带上CATCH_前缀只有日志/消息宏(UNSCOPED_)INFO、WARN、(UNSCOPED_)CAPTURE与外部宏撞名时用CATCH_CONFIG_PREFIX_MESSAGES就够了影响面更小。CATCH_CONFIG_PREFIX_MESSAGES是后来引入的见 docs/release-notes.md 中 “IntroducedCATCH_CONFIG_PREFIX_MESSAGESto prefix only logging macros (#2544)”。在构建中定义前缀宏CMake 项目Catch2 仓库自带的回归测试展示了标准写法。tests/ExtraTests/CMakeLists.txt 中add_executable(PrefixedMacros ${TESTS_DIR}/X01-PrefixedMacros.cpp) target_compile_definitions(PrefixedMacros PRIVATE CATCH_CONFIG_PREFIX_ALL CATCH_CONFIG_RUNTIME_STATIC_REQUIRE) # We want to verify that the main library can also be built with prefixed # macros, regression test for #3087. target_link_libraries(PrefixedMacros Catch2_buildall_interface)这里有三个要点定义加在测试目标上target_compile_definitions即对你自己的测试代码的所有编译单元生效——前缀宏必须在使用这些宏的编译单元里定义链接Catch2_buildall_interface而不是预编译库因为要同时验证主库也能带CATCH_CONFIG_PREFIX_ALL构建这是对 #3087 的回归测试主库在该宏定义时构建失败的 bug 已在 docs/release-notes.md 中记录为修复项如果你的测试代码与 Catch2 库源码分开预编译注意库一侧也需要按前缀模式构建两边保持一致如果你的项目是通过 Catch2 的 CMake 包整体配置库构建的CMake/CatchConfigOptions.cmake 提供了对应的 CMake 选项CATCH_CONFIG_PREFIX_ALL和CATCH_CONFIG_PREFIX_MESSAGES默认 OFF标记为 advanced用于控制 Catch2 库自身的编译配置。非 CMake 或直接用编译器标志在测试源文件所在编译命令里直接定义该宏即可例如 GCC/Clangg -stdc17 -DCATCH_CONFIG_PREFIX_ALL your_test.cpp ...如果只处理消息宏冲突把宏换成CATCH_CONFIG_PREFIX_MESSAGES。改写测试代码前缀宏长什么样仓库里的 tests/ExtraTests/X01-PrefixedMacros.cpp 是一份可直接参考的前缀宏用法示例它混用了测试宏、断言宏、匹配器和消息宏CATCH_TEST_CASE(PrefixedMacros) { using namespace Catch::Matchers; CATCH_REQUIRE( 1 1 ); CATCH_REQUIRE_FALSE( 1 ! 1 ); CATCH_REQUIRE_THROWS(this_throws()); CATCH_REQUIRE_THROWS_AS(this_throws(), std::runtime_error); CATCH_REQUIRE_THROWS_WITH(this_throws(), Some msg); CATCH_REQUIRE_NOTHROW(this_doesnt_throw()); CATCH_CHECK( 1 1 ); CATCH_CHECKED_IF( 1 1 ) { CATCH_SUCCEED(dont care); } CATCH_CHECKED_ELSE ( 1 1 ) { CATCH_SUCCEED(dont care); } CATCH_REQUIRE_THAT(abcd, Equals(abcd)); CATCH_CHECK_THAT(bdef, Equals(bdef)); CATCH_INFO( some info ); CATCH_UNSCOPED_INFO( some info ); CATCH_WARN( some warn ); CATCH_SECTION(some section) { int i 1; CATCH_CAPTURE( i ); CATCH_UNSCOPED_CAPTURE( i 2, i 3 ); CATCH_DYNAMIC_SECTION(Dynamic section: i) { CATCH_FAIL_CHECK( failure ); } } CATCH_STATIC_REQUIRE( std::is_voidvoid::value ); CATCH_FAIL(); }改写规则很机械把原宏名前面加上CATCH_即可例如TEST_CASE→CATCH_TEST_CASE、REQUIRE→CATCH_REQUIRE、SECTION→CATCH_SECTION、INFO/UNSCOPED_INFO/WARN/CAPTURE→CATCH_INFO等。注意该示例文件头部注释说明了它有意不覆盖全部宏“We intentionally do not provide full coverage of all macros”文件末尾还列出了一批未测试的前缀宏如CATCH_TEST_CASE_METHOD、CATCH_SCENARIO等供回归时补充不要把它当成前缀宏的完整清单。验证前缀是否真正生效仓库的 CTest 检查给出了可复用的判定方式tests/ExtraTests/CMakeLists.txtadd_test(NAME CATCH_CONFIG_PREFIX_ALL COMMAND PrefixedMacros -s) set_tests_properties(CATCH_CONFIG_PREFIX_ALL PROPERTIES PASS_REGULAR_EXPRESSION CATCH_ FAIL_REGULAR_EXPRESSION # The spaces are important - They disambiguate between CATCH_REQUIRE # and REQUIRE without prefix. REQUIRE; REQUIRE_FALSE; REQUIRE_THROWS; ...; CHECK_THAT )翻译成手动验证就是用-s详细输出运行测试二进制确认测试正常执行输出中应出现带CATCH_前缀的宏名输出中不应再出现无前缀的断言宏名。注意匹配时要带前导空格如REQUIRE这样才能区分CATCH_REQUIRE和独立的REQUIRE。编译层面同样要确认定义前缀宏后测试工程能完整编译通过且如果 Catch2 库源码参与你的构建库自身不带该宏冲突地构建成功。限制与已知问题前缀宏是编译期配置必须覆盖所有使用 Catch 宏的编译单元只改部分翻译单元会导致一部分代码用REQUIRE、另一部分用CATCH_REQUIRE行为不一致。历史上CATCH_CONFIG_PREFIX_ALL定义时主库构建失败的问题#3087已修复tests/ExtraTests/CMakeLists.txt 中的PrefixedMacros目标就是它的回归测试如果你在较旧版本上遇到“定义了前缀宏但链接/构建库出错”优先核对是否命中此回归。只想要小范围改动时选CATCH_CONFIG_PREFIX_MESSAGES它只改消息宏命名其余宏保持短名两个宏都定义时前缀行为由CATCH_CONFIG_PREFIX_MESSAGES的推导逻辑决定参见 src/catch2/internal/catch_config_prefix_messages.hpp 的注释CATCH_CONFIG_PREFIX_ALL可以借用来避免与其他宏冲突实际建议按上文的适用范围二选一不要混用。若冲突并非来自 Catch 宏而是 Catch2 内部宏与外部宏撞名前缀宏帮不上忙——前缀只作用于用户宏内部命名冲突需要升级 Catch2 版本例如 docs/release-notes.md 记录了内部弃用宏重命名为CATCH_DEPRECATED以避免冲突的 #3058 修改。【免费下载链接】Catch2A modern, C-native, test framework for unit-tests, TDD and BDD - using C14, C17 and later (C11 support is in v2.x branch, and C03 on the Catch1.x branch)项目地址: https://gitcode.com/GitHub_Trending/ca/Catch2创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考
Catch2 测试宏与平台头文件命名冲突时如何用前缀宏解决【免费下载链接】Catch2A modern, C-native, test framework for unit-tests, TDD and BDD - using C14, C17 and later (C11 support is in v2.x branch, and C03 on the Catch1.x branch)项目地址: https://gitcode.com/GitHub_Trending/ca/Catch2如果你在用 Catch2 写测试时编译报错指向TEST_CASE、REQUIRE这类短宏名而报错源头是某个平台头文件或被测试代码里恰好定义了同名宏问题通常出在 Catch2 的用户宏与外部标识符撞名。Catch2 的官方做法是定义CATCH_CONFIG_PREFIX_ALL让所有 Catch 用户宏加上CATCH_前缀例如CATCH_TEST_CASE、CATCH_REQUIRE或者定义CATCH_CONFIG_PREFIX_MESSAGES只给消息宏加前缀。这篇文章说明怎么选、怎么定义以及如何验证前缀确实生效。什么情况下会冲突以及两个前缀宏的适用范围docs/configuration.md 在 “Prefixing Catch macros” 一节解释了背景为了保持测试代码干净Catch 使用短宏名如TEST_CASE和REQUIRE。文档原话是这些短名偶尔会与平台头文件或被测试系统system under test中的标识符冲突此时定义下面两个宏之一即可CATCH_CONFIG_PREFIX_ALL // Prefix all macros with CATCH_ CATCH_CONFIG_PREFIX_MESSAGES // Prefix only message macros ((UNSCOPED_)INFO, WARN, (UNSCOPED_)CAPTURE)选择标准按冲突面大小来冲突涉及TEST_CASE、REQUIRE等通用测试宏时用CATCH_CONFIG_PREFIX_ALL它让所有Catch 用户宏带上CATCH_前缀只有日志/消息宏(UNSCOPED_)INFO、WARN、(UNSCOPED_)CAPTURE与外部宏撞名时用CATCH_CONFIG_PREFIX_MESSAGES就够了影响面更小。CATCH_CONFIG_PREFIX_MESSAGES是后来引入的见 docs/release-notes.md 中 “IntroducedCATCH_CONFIG_PREFIX_MESSAGESto prefix only logging macros (#2544)”。在构建中定义前缀宏CMake 项目Catch2 仓库自带的回归测试展示了标准写法。tests/ExtraTests/CMakeLists.txt 中add_executable(PrefixedMacros ${TESTS_DIR}/X01-PrefixedMacros.cpp) target_compile_definitions(PrefixedMacros PRIVATE CATCH_CONFIG_PREFIX_ALL CATCH_CONFIG_RUNTIME_STATIC_REQUIRE) # We want to verify that the main library can also be built with prefixed # macros, regression test for #3087. target_link_libraries(PrefixedMacros Catch2_buildall_interface)这里有三个要点定义加在测试目标上target_compile_definitions即对你自己的测试代码的所有编译单元生效——前缀宏必须在使用这些宏的编译单元里定义链接Catch2_buildall_interface而不是预编译库因为要同时验证主库也能带CATCH_CONFIG_PREFIX_ALL构建这是对 #3087 的回归测试主库在该宏定义时构建失败的 bug 已在 docs/release-notes.md 中记录为修复项如果你的测试代码与 Catch2 库源码分开预编译注意库一侧也需要按前缀模式构建两边保持一致如果你的项目是通过 Catch2 的 CMake 包整体配置库构建的CMake/CatchConfigOptions.cmake 提供了对应的 CMake 选项CATCH_CONFIG_PREFIX_ALL和CATCH_CONFIG_PREFIX_MESSAGES默认 OFF标记为 advanced用于控制 Catch2 库自身的编译配置。非 CMake 或直接用编译器标志在测试源文件所在编译命令里直接定义该宏即可例如 GCC/Clangg -stdc17 -DCATCH_CONFIG_PREFIX_ALL your_test.cpp ...如果只处理消息宏冲突把宏换成CATCH_CONFIG_PREFIX_MESSAGES。改写测试代码前缀宏长什么样仓库里的 tests/ExtraTests/X01-PrefixedMacros.cpp 是一份可直接参考的前缀宏用法示例它混用了测试宏、断言宏、匹配器和消息宏CATCH_TEST_CASE(PrefixedMacros) { using namespace Catch::Matchers; CATCH_REQUIRE( 1 1 ); CATCH_REQUIRE_FALSE( 1 ! 1 ); CATCH_REQUIRE_THROWS(this_throws()); CATCH_REQUIRE_THROWS_AS(this_throws(), std::runtime_error); CATCH_REQUIRE_THROWS_WITH(this_throws(), Some msg); CATCH_REQUIRE_NOTHROW(this_doesnt_throw()); CATCH_CHECK( 1 1 ); CATCH_CHECKED_IF( 1 1 ) { CATCH_SUCCEED(dont care); } CATCH_CHECKED_ELSE ( 1 1 ) { CATCH_SUCCEED(dont care); } CATCH_REQUIRE_THAT(abcd, Equals(abcd)); CATCH_CHECK_THAT(bdef, Equals(bdef)); CATCH_INFO( some info ); CATCH_UNSCOPED_INFO( some info ); CATCH_WARN( some warn ); CATCH_SECTION(some section) { int i 1; CATCH_CAPTURE( i ); CATCH_UNSCOPED_CAPTURE( i 2, i 3 ); CATCH_DYNAMIC_SECTION(Dynamic section: i) { CATCH_FAIL_CHECK( failure ); } } CATCH_STATIC_REQUIRE( std::is_voidvoid::value ); CATCH_FAIL(); }改写规则很机械把原宏名前面加上CATCH_即可例如TEST_CASE→CATCH_TEST_CASE、REQUIRE→CATCH_REQUIRE、SECTION→CATCH_SECTION、INFO/UNSCOPED_INFO/WARN/CAPTURE→CATCH_INFO等。注意该示例文件头部注释说明了它有意不覆盖全部宏“We intentionally do not provide full coverage of all macros”文件末尾还列出了一批未测试的前缀宏如CATCH_TEST_CASE_METHOD、CATCH_SCENARIO等供回归时补充不要把它当成前缀宏的完整清单。验证前缀是否真正生效仓库的 CTest 检查给出了可复用的判定方式tests/ExtraTests/CMakeLists.txtadd_test(NAME CATCH_CONFIG_PREFIX_ALL COMMAND PrefixedMacros -s) set_tests_properties(CATCH_CONFIG_PREFIX_ALL PROPERTIES PASS_REGULAR_EXPRESSION CATCH_ FAIL_REGULAR_EXPRESSION # The spaces are important - They disambiguate between CATCH_REQUIRE # and REQUIRE without prefix. REQUIRE; REQUIRE_FALSE; REQUIRE_THROWS; ...; CHECK_THAT )翻译成手动验证就是用-s详细输出运行测试二进制确认测试正常执行输出中应出现带CATCH_前缀的宏名输出中不应再出现无前缀的断言宏名。注意匹配时要带前导空格如REQUIRE这样才能区分CATCH_REQUIRE和独立的REQUIRE。编译层面同样要确认定义前缀宏后测试工程能完整编译通过且如果 Catch2 库源码参与你的构建库自身不带该宏冲突地构建成功。限制与已知问题前缀宏是编译期配置必须覆盖所有使用 Catch 宏的编译单元只改部分翻译单元会导致一部分代码用REQUIRE、另一部分用CATCH_REQUIRE行为不一致。历史上CATCH_CONFIG_PREFIX_ALL定义时主库构建失败的问题#3087已修复tests/ExtraTests/CMakeLists.txt 中的PrefixedMacros目标就是它的回归测试如果你在较旧版本上遇到“定义了前缀宏但链接/构建库出错”优先核对是否命中此回归。只想要小范围改动时选CATCH_CONFIG_PREFIX_MESSAGES它只改消息宏命名其余宏保持短名两个宏都定义时前缀行为由CATCH_CONFIG_PREFIX_MESSAGES的推导逻辑决定参见 src/catch2/internal/catch_config_prefix_messages.hpp 的注释CATCH_CONFIG_PREFIX_ALL可以借用来避免与其他宏冲突实际建议按上文的适用范围二选一不要混用。若冲突并非来自 Catch 宏而是 Catch2 内部宏与外部宏撞名前缀宏帮不上忙——前缀只作用于用户宏内部命名冲突需要升级 Catch2 版本例如 docs/release-notes.md 记录了内部弃用宏重命名为CATCH_DEPRECATED以避免冲突的 #3058 修改。【免费下载链接】Catch2A modern, C-native, test framework for unit-tests, TDD and BDD - using C14, C17 and later (C11 support is in v2.x branch, and C03 on the Catch1.x branch)项目地址: https://gitcode.com/GitHub_Trending/ca/Catch2创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考
并行执行与性能优化实战)
