Repository navigation
Conversation
ludfjig
force-pushed
the
experimental-build-runtime
branch
from
November 13, 2026 00:55
71e1b5a to
32aefd7
Compare
ludfjig
force-pushed
the
experimental-build-runtime
branch
2 times, most recently
from
November 16, 2026 18:46
efedd2e to
6d5e1ba
Compare
ludfjig
force-pushed
the
experimental-build-runtime
branch
2 times, most recently
from
November 17, 2026 18:45
5b62b8a to
4318aab
Compare
ludfjig
force-pushed
the
experimental-build-runtime
branch
from
November 17, 2026 19:33
4318aab to
00ead69
Compare
ludfjig
force-pushed
the
experimental-build-runtime
branch
2 times, most recently
from
November 17, 2026 21:39
0aca748 to
1638a53
Compare
Add an experimental hyperlight-wasm-aot subcommand that builds a guest runtime for a WIT world. C API and .NET users can then build a runtime without a hyperlight-wasm checkout and without cargo-hyperlight. Installed from crates.io, the tool embeds the runtime source. In a checkout it builds the workspace's runtime in place. The guest macro accepts a .wit file or a directory of .wit files in WIT_WORLD, so no wasm-tools step is needed. Hyperlight.Wasm.Build runs the subcommand for HyperlightWit items with Runtime set, and precompiles HyperlightComponent items, so dotnet build creates both. This is opt-in, because it needs Rust. CI builds the .NET tests' runtime with the subcommand in the examples job, which already compiles hyperlight-wasm-aot, and ships it with the modules. One test leg builds the runtime and component through Hyperlight.Wasm.Build instead. Signed-off-by: Ludvig Liljenberg <4257730+ludfjig@users.noreply.github.com>
ludfjig
force-pushed
the
experimental-build-runtime
branch
from
November 17, 2026 22:16
1638a53 to
21672fa
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Using the C API or .NET packages needs a guest runtime built for the component's WIT world. That takes a hyperlight-wasm checkout, cargo-hyperlight and wasm-tools.
This adds
hyperlight-wasm-aot experimental-build-runtime <wit> <output>. Installed from crates.io, the tool carries the runtime source and builds it with the cargo-hyperlight library, so users need only rustup and clang. The guest macro accepts a.witfile or directory inWIT_WORLD.Hyperlight.Wasm.Buildcan run it during the build. WithRuntimeset on aHyperlightWititem,dotnet buildcreates the runtime, andHyperlightComponentitems are precompiled to.aot. Both go in the output directory. This is opt-in because it needs Rust.CI builds the .NET tests' runtime with the subcommand and ships it with the example modules, so the .NET tests run it. One test leg builds the runtime and component through
Hyperlight.Wasm.Buildinstead. CI covers the checkout path. The installed path was verified manually.Based on #564.