Allow specifiying relative paths in the --file
option without *
#4180
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.
With this modification, the
--file
option would allow passing paths with folder prefixes.Consider a compilation json that contains a
.
in the directory fields, with the following example directory layout:Before this patch, you could only specify path to source files with the
--file
option, that were not absolute is to add a*
before the directory name.CodeChecker analyze ./compile_commnands.json -o ./reports --file "*src/b.cpp"
After this patch the following two methods will also work:
CodeChecker analyze ./compile_commnands.json -o ./reports --file "./src/b.cpp"
CodeChecker analyze ./compile_commnands.json -o ./reports --file "src/b.cpp"
TBD.: