Skip to content

Conversation

@phlax
Copy link
Contributor

@phlax phlax commented Jan 13, 2026

No description provided.

Signed-off-by: Ryan Northey <ryan@synca.io>
bazel_dep(name = "rules_license", version = "1.0.0")
bazel_dep(name = "rules_python", version = "1.7.0")
bazel_dep(name = "rules_rust", version = "0.68.1")

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@leonm1 this currently has no llvm toolchain setup - it should have it added as a dev_dependency

it wont prevent consumers from using it - but you will need the toolchain setup in order to test bzlmod

use_repo(wamr, "com_github_bytecodealliance_wasm_micro_runtime")

# V8 runtime and its dependencies
v8 = use_extension("//bazel:extensions.bzl", "v8")
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ideally we add a v8 (and friends) bzlmod

)

# WasmEdge runtime
wasmedge = use_extension("//bazel:extensions.bzl", "wasmedge")
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this file was originally bot generated - this is probably correct - but we dont test this in envoy

@phlax
Copy link
Contributor Author

phlax commented Jan 21, 2026

format issue looks like another bug in rules_rust - it appears to be detecting whether bzlmod is enabled by the presence of MODULE.bazel - which is very much not correct (or at least it needs to enable bzlmod in that case)

bazelbuild/rules_rust#3815

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant