Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GraalVM engine toolchains #51

Open
Tracked by #24
sgammon opened this issue Aug 23, 2023 · 0 comments
Open
Tracked by #24

GraalVM engine toolchains #51

sgammon opened this issue Aug 23, 2023 · 0 comments
Assignees
Labels
feature Mainline feature work
Milestone

Comments

@sgammon
Copy link
Owner

sgammon commented Aug 23, 2023

It would be great to expose GraalVM language engines, like js and wasm (GraalJs and GraalWasm) using Bazel's Toolchains feature. This would let other rules and downstream projects resolve these for their own purposes.

We can also register these language binaries, in some cases, as language-native toolchain types, as we've already done for Java toolchain use of GraalVM as a JVM. But we should probably treat this separately, since in some cases projects will need to resolve specifically the GraalVM implementations of these engines, and the regular toolchain system isn't really equipped to guarantee that.

@sgammon sgammon added the feature Mainline feature work label Aug 23, 2023
@sgammon sgammon added this to the 1.0.0 milestone Aug 23, 2023
@sgammon sgammon self-assigned this Aug 23, 2023
@sgammon sgammon mentioned this issue Aug 23, 2023
22 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Mainline feature work
Projects
Development

No branches or pull requests

1 participant