Setup a release action for producing binaries #12
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 PR adds a release action that compiles LLVM and attaches the resulting binaries to the release. It takes the branch from which the release is made into account and incorporates it into the name of the attached tarball.
It currently uses the following naming format for the binaries:
${{RELEASE_TAG}}-llvm-${{OS}}-${{ARCH}}-${{BRANCH}}, whereRELEASE_TAGis the tag of the release,OSis currently only Linux,ARCHis currently x86 64-bit and aarch64, andBRANCHis the source branch of the release. This turns the resulting URLs into:ocaml-flambda/llvm-project/releases/download/${{ RELEASE_TAG }}/${{BINARY_NAME}}.tar.gz, whereBINARY_NAMEis the name of the binary described above.Testing I've created an example release here that used the action to produce the binaries: https://github.com/ocaml-flambda/llvm-project/releases/tag/test-release-v7. I've tried out the resulting binary in the following run: https://github.com/ocaml-flambda/llvm-project/actions/runs/16775365155. (These were tried before the name format change discussed below.)