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.
This adds
llvm-full
. The main difference tollvm
is that this contains headers for Clang and LLVM, static libraries for them, and additional tools likellvm-config
(often required when building a tool that interacts with LLVM).-full
might not be the most descriptive suffix. It suggests that all tools from LLVM are included and, to some extent, that these builds are built to support plugin development, but they only contain static libraries for the components. Would love some suggestions.I have never contributed to a bucket, so I don't know the exact conventions. Since
llvm
comes in two manifests, I want to replicate that here, because LLVM 19, for example, doesn't include full builds for arm64. Similarly, the beta versions of LLVM 20.1 didn't include a build for arm64 either. Can I include the arm64 version in here, or should I open another PR? I currently just mentioned thatllvm-full-arm64
will exist at some point.Closes #6402
<manifest-name[@version]|chore>: <general summary of the pull request>