build: exclude mptest target from compile commands
What changed, and why it matters
This is a minor build-system tweak. It adds one internal test target ('mptest') to a list of targets that should not be included in the compile_commands.json database used by developer tools like clang-tidy. There is no user-facing or security-relevant change.
No security action needed. Treat as routine build maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies cmake/libmultiprocess.cmake to add ‘mptest’ to the set_target_properties call that disables EXPORT_COMPILE_COMMANDS. This prevents generated C++ source files for the mptest target from causing warnings in tools that consume the compilation database. It is a developer-experience fix, not a code or runtime change.
Changed components
cmake/libmultiprocess.cmakeInspect captured patch +1 / −1
diff --git a/cmake/libmultiprocess.cmake b/cmake/libmultiprocess.cmake
index 027109a9..0dab1f66 100644
--- a/cmake/libmultiprocess.cmake
+++ b/cmake/libmultiprocess.cmake
@@ -34,5 +34,5 @@ function(add_libmultiprocess subdir)
# exclusion, tools like clang-tidy and IWYU that make use of compilation
# database would complain that the generated c++ source files do not exist. An
# alternate fix could build "mpexamples" by default like "mptests" above.
- set_target_properties(mpcalculator mpprinter mpexample PROPERTIES EXPORT_COMPILE_COMMANDS OFF)
+ set_target_properties(mpcalculator mpprinter mpexample mptest PROPERTIES EXPORT_COMPILE_COMMANDS OFF)
endfunction()
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.