Copy the generated JS runtime into OUT_DIR

Open
#296 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
build-system

Research direction

Trace the build logic that produces target/hyperlight-js-runtime and the include_bytes! reference. Verify how OUT_DIR is handled during clean and cached builds. Done means the final runtime binary is copied into OUT_DIR and include_bytes! reads that copy, avoiding stale or missing cached runtimes.

Written by the indexing model from the issue text.

Description

lifecycle/needs-review

The generated runtime binary is stored under target/hyperlight-js-runtime, outside OUT_DIR. Cached builds can therefore use a stale or missing runtime. This is annoying and should be fixed, I believe by copying the final binary to OUT_DIR, and include_bytes! the file in OUT_DIR instead of the external location.

Relates to https://github.com/hyperlight-dev/hyperlight-wasm/issues/547

Dominant language
Rust
Stars
13
Forks
5
Avg merge
8d 10h
Merged PRs (30d)
13

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hyperlight-dev/hyperlight-js

All issues in hyperlight-dev/hyperlight-js

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.