parallaxsecond / parallaxsecond/rust-tss-esapi
Request: MUSL x-compilation target
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 135
- Forks
- 80
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 5
Description
The currently supported targets list includes a bunch of GNU target toolchains, but none on MUSL. In order to build fully static binaries - like something one might want to run inside the initramfs, we need to separate from whatever libc is used by the rest of the host inside that target as it might change and break critical paths accessing the TPM before a full userspace is available. The crate page has a link to how cross compiles are set up in the buildbots, but leads to a missing page - We include cross-compilation builds as a nightly check in Github Actions - you can find them here as an example of the steps needed
Is there a writeup somewhere on how to set this up, or possibly a way to include pre-built targets?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the crate page's supported-target list and the broken cross-compilation link, then compare the referenced rust-tss-esapi/tests/cross-compile.sh setup. Determine whether the contribution should document or add a MUSL target or provide pre-built targets. Done means the chosen approach supports a verifiable fully static cross-build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100