Prefer matching llvm-config
in find-llvm-config
#13087
Merged
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.
Even if the command
llvm-config
exists and its version matches, any otherllvm-config*
command with the same version would currently be preferred. That was unexpected for me.I think it makes sense that
llvm-config
has preference.For example, if you have both
llvm-config
andllvm-config14
in your path, the results would bellvm-config14
in master andllvm-config
with this patch.