hyperlight-dev / hyperlight-dev/hyperlight-wasm
Copy the generated guest runtime into OUT_DIR
Open
Nobody has claimed this yet.
lifecycle/needs review
- Dominant language
- Rust
- Stars
- 728
- Forks
- 39
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 23
Description
The generated runtime binary is stored under target/hyperlight-wasm-runtime, outside OUT_DIR. Cached builds can therefore use a stale or missing runtime. This is annoying and should be fixed by copying the final binary into OUT_DIR (I think this would fix it), and include_bytes! the file in OUT_DIR instead of external file
Contributor guide
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
Locate the build logic that generates target/hyperlight-wasm-runtime and the include_bytes! reference to the external runtime file. Run a cached build to reproduce the stale or missing runtime, then verify that the final binary is copied into OUT_DIR and loaded from there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100