The path for compile_commands.json is hardcoded to CMAKE_BINARY_DIR #6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
We can use CPM like this CPMAddPackage( |
Owner
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The path for compile_commands.json is hardcoded to CMAKE_BINARY_DIR. In case of building it as a standalone project the CMAKE_CURRENT_BINARY_DIR and CMAKE_BINARY_DIR are the same, but in case of building with CPM, or other ways where it is in some subdirectory, it will create the compile_commands.json in the CMAKE_BINARY_DIR, and try to copy it from CMAKE_CURRENT_BINARY_DIR, and it will fail.
https://github.com/Kitware/CMake/blob/572f3105c1a011854c29d7764d5c89312c0c8932/Source/cmGlobalNinjaGenerator.cxx#L1219