bazel
/
rules_rust
mirror of https://github.com/bazelbuild/rules_rust
2
0
Fork 0
Code Issues Releases Activity
rules_rust/MODULE.bazel

187 lines
5.1 KiB
Plaintext
Raw Normal View History

Updated direct dependencies (#2308)
2023-12-06 18:47:47 +00:00
"""bazelbuild/rules_rust"""
Support bzlmod (#1528) This makes rules_rust load dependencies via bzlmod. Currently only basic functionality is completed, such as registering rustc toolchains and compiling crates. Note that it cannot interact with cargo, wasm or load any other rust toolchains such as rustfmt. There is one new module, `examples/bzlmod/hello_world`, that depends on the root `rules_rust` module. This example can be built and run using: ``` cd examples/bzlmod/hello_world bazel run //:hello_world ``` To register toolchains in an ergonomic way, it defines a new "hub" repository that contains all the toolchain proxies, so they can all be registered like so: ``` register_toolchains("@rust_toolchains//:all") ``` closes https://github.com/bazelbuild/rules_rust/issues/1493
2023-03-29 08:56:01 +00:00
module(
name = "rules_rust",
Release version 53.0 (#2949)
2024-10-18 18:01:09 +00:00
version = "0.53.0",
Support bzlmod (#1528) This makes rules_rust load dependencies via bzlmod. Currently only basic functionality is completed, such as registering rustc toolchains and compiling crates. Note that it cannot interact with cargo, wasm or load any other rust toolchains such as rustfmt. There is one new module, `examples/bzlmod/hello_world`, that depends on the root `rules_rust` module. This example can be built and run using: ``` cd examples/bzlmod/hello_world bazel run //:hello_world ``` To register toolchains in an ergonomic way, it defines a new "hub" repository that contains all the toolchain proxies, so they can all be registered like so: ``` register_toolchains("@rust_toolchains//:all") ``` closes https://github.com/bazelbuild/rules_rust/issues/1493
2023-03-29 08:56:01 +00:00
)
Mark the bzlmod extension reproducible as appropriate (#2575) @matts1 @fmeum PTAL :)
2024-03-27 15:38:30 +00:00
bazel_dep(
name = "bazel_features",
version = "1.9.1",
)
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
bazel_dep(
name = "bazel_skylib",
version = "1.5.0",
)
bazel_dep(
name = "platforms",
version = "0.0.8",
)
bazel_dep(
name = "rules_cc",
version = "0.0.9",
)
Generate package license metadata (#2476) #2475
2024-02-14 00:37:38 +00:00
bazel_dep(
name = "rules_license",
version = "0.0.8",
)
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
bazel_dep(
name = "rules_proto",
Support incompatible enable proto toolchain resolution (#2741) This allows using a shared (generally pre-built) protoc definition, rather than needing to supply one via a label. We allow (but deprecate) users to still bring along their own protoc as a label, but if they want to do so, they will need to ensure they have the correct repositories registered in order to build/bring their protoc, rather than us setting them up by default.
2024-07-19 08:10:10 +00:00
version = "6.0.2",
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
)
Support cargo_bazel_bootstrap for bzlmod (#2021) I've pulled out some of the code from https://github.com/bazelbuild/rules_rust/pull/1910 into a seperate PR, to simplify the review process. --------- Co-authored-by: scentini <rosica@google.com>
2023-10-25 14:23:31 +00:00
bazel_dep(
name = "apple_support",
Update apple rules (#2506) Fixes https://github.com/bazelbuild/rules_rust/issues/2495
2024-02-21 09:27:30 +00:00
version = "1.13.0",
Support cargo_bazel_bootstrap for bzlmod (#2021) I've pulled out some of the code from https://github.com/bazelbuild/rules_rust/pull/1910 into a seperate PR, to simplify the review process. --------- Co-authored-by: scentini <rosica@google.com>
2023-10-25 14:23:31 +00:00
repo_name = "build_bazel_apple_support",
)
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
bazel_dep(
name = "protobuf",
version = "21.7",
repo_name = "com_google_protobuf",
)
Add aspect_rules_js to MODULE.bazel (#2618) Otherwise wasm_bindgen with rules_js is unusable.
2024-04-23 09:58:13 +00:00
bazel_dep(
name = "aspect_rules_js",
version = "1.39.0",
)
Support bzlmod (#1528) This makes rules_rust load dependencies via bzlmod. Currently only basic functionality is completed, such as registering rustc toolchains and compiling crates. Note that it cannot interact with cargo, wasm or load any other rust toolchains such as rustfmt. There is one new module, `examples/bzlmod/hello_world`, that depends on the root `rules_rust` module. This example can be built and run using: ``` cd examples/bzlmod/hello_world bazel run //:hello_world ``` To register toolchains in an ergonomic way, it defines a new "hub" repository that contains all the toolchain proxies, so they can all be registered like so: ``` register_toolchains("@rust_toolchains//:all") ``` closes https://github.com/bazelbuild/rules_rust/issues/1493
2023-03-29 08:56:01 +00:00
use bazel_ci_rules bazel_dep instead of http_archive (#2678) bazel_ci_rules@1.0.0 module has been published to the BCR, see https://github.com/bazelbuild/bazel-central-registry/pull/2058 This use it has a bazel_dep instead of a http_archive Signed-off-by: Matthieu MOREL <matthieu.morel35@gmail.com>
2024-06-06 10:28:40 +00:00
bazel_dep(
name = "bazel_ci_rules",
version = "1.0.0",
dev_dependency = True,
)
Support building more things with bzlmod (#2601) This allows us to build more things with bzlmod with `WORKSPACE.bazel` disabled. This is required because when you use it as a module, it can't load dependencies from `WORKSPACE.bazel`. `bazel build --enable_bzlmod --noenable_workspace --lockfile_mode=off //... --keep_going` Before: Analysis succeeded for 937 of 978 top-level targets After: Analysis succeeded for 978 of 982 top-level targets Once we get those remaining targets working, we can then change our CI to add `--noenable_workspace` to our bzlmod configuration.
2024-04-03 15:38:38 +00:00
bazel_dep(
name = "rules_python",
version = "0.31.0",
dev_dependency = True,
)
bazel_dep(
name = "rules_testing",
version = "0.6.0",
dev_dependency = True,
)
Fix bzlmod examples on windows (#2454) On windows (and some other platforms), the file extension of cargo, rustc, etc have an extension. The module extension for loading crates did not take this into account, causing it to error on windows. Additionally, when using bzlmod to build vendored crates, the runfiles tree would exceed the 260 char windows path limit. To mitigate this, I have shortened the internal_deps module extension to just `i` and changed the build script suffix to `_bs` from `_build_script`. This makes the path names below the 260 char limit. This makes the bzlmod CI run on windows, to avoid regressing this. Currently gen_rust_project does not run on windows for other reasons, although we do build this.
2024-02-23 12:55:58 +00:00
internal_deps = use_extension("//rust/private:extensions.bzl", "i")
Support bzlmod (#1528) This makes rules_rust load dependencies via bzlmod. Currently only basic functionality is completed, such as registering rustc toolchains and compiling crates. Note that it cannot interact with cargo, wasm or load any other rust toolchains such as rustfmt. There is one new module, `examples/bzlmod/hello_world`, that depends on the root `rules_rust` module. This example can be built and run using: ``` cd examples/bzlmod/hello_world bazel run //:hello_world ``` To register toolchains in an ergonomic way, it defines a new "hub" repository that contains all the toolchain proxies, so they can all be registered like so: ``` register_toolchains("@rust_toolchains//:all") ``` closes https://github.com/bazelbuild/rules_rust/issues/1493
2023-03-29 08:56:01 +00:00
use_repo(
internal_deps,
Expose crates_vendor deps to bzlmod (#2372) Without this, I have been unable to update https://github.com/dtolnay/cxx to bzlmod. When I run `bazel run //third-party:vendor` ([this rule](https://github.com/dtolnay/cxx/blob/3c1bcc012f285dc59d39143e658df67659142cd1/third-party/BUILD#L3-L11)) it failed with **"unknown repo 'cargo_bazel.buildifier-linux-amd64' requested from @@rules_rust~0.35.0"**: ```console ERROR: no such package '@@[unknown repo 'cargo_bazel.buildifier-linux-amd64' requested from @@rules_rust~0.35.0]//file': The repository '@@[unknown repo 'cargo_bazel.buildifier-linux-amd64' requested from @@rules_rust~0.35.0]' could not be resolved: No repository visible as '@cargo_bazel.buildifier-linux-amd64' from repository '@@rules_rust~0.35.0' ERROR: ~/.cache/bazel/_bazel_david/ebce1d0721fb68dda9c70c0dd1405803/external/rules_rust~0.35.0/crate_universe/private/vendor/BUILD.bazel:3:27: no such package '@@[unknown repo 'cargo_bazel.buildifier-linux-amd64' requested from @@rules_rust~0.35.0]//file': The repository '@@[unknown repo 'cargo_bazel.buildifier-linux-amd64' requested from @@rules_rust~0.35.0]' could not be resolved: No repository visible as '@cargo_bazel.buildifier-linux-amd64' from repository '@@rules_rust~0.35.0' and referenced by '@@rules_rust~0.35.0//crate_universe/private/vendor:buildifier' ERROR: Analysis of target '//third-party:vendor' failed; build aborted: Analysis failed ``` After this change, it works. My MODULE.bazel can be seen in https://github.com/dtolnay/cxx/pull/1294.
2023-12-28 18:53:57 +00:00
"cargo_bazel.buildifier-darwin-amd64",
"cargo_bazel.buildifier-darwin-arm64",
"cargo_bazel.buildifier-linux-amd64",
"cargo_bazel.buildifier-linux-arm64",
"cargo_bazel.buildifier-windows-amd64.exe",
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
"cui",
Added Rust 1.82.0 (#2944) https://blog.rust-lang.org/2024/10/17/Rust-1.82.0.html
2024-10-21 05:39:37 +00:00
"cui__anyhow-1.0.89",
"cui__camino-1.1.9",
"cui__cargo-lock-10.0.0",
"cui__cargo-platform-0.1.7",
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
"cui__cargo_metadata-0.18.1",
Added Rust 1.82.0 (#2944) https://blog.rust-lang.org/2024/10/17/Rust-1.82.0.html
2024-10-21 05:39:37 +00:00
"cui__cargo_toml-0.20.5",
Updated platform triple mapping to support T3 platforms without `std`. (#2899) This change allows for the definition of platform constraints without introducing plumbing in repository rules that would attempt to fetch artifacts that do not exist. --------- Co-authored-by: Daniel Wagner-Hall <dwagnerhall@apple.com>
2024-10-01 20:31:32 +00:00
"cui__cfg-expr-0.17.0",
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
"cui__clap-4.3.11",
Added Rust 1.82.0 (#2944) https://blog.rust-lang.org/2024/10/17/Rust-1.82.0.html
2024-10-21 05:39:37 +00:00
"cui__crates-index-3.2.0",
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
"cui__hex-0.4.3",
Added Rust 1.82.0 (#2944) https://blog.rust-lang.org/2024/10/17/Rust-1.82.0.html
2024-10-21 05:39:37 +00:00
"cui__indoc-2.0.5",
"cui__itertools-0.13.0",
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
"cui__maplit-1.0.2",
Added Rust 1.82.0 (#2944) https://blog.rust-lang.org/2024/10/17/Rust-1.82.0.html
2024-10-21 05:39:37 +00:00
"cui__normpath-1.3.0",
"cui__once_cell-1.20.2",
"cui__pathdiff-0.2.2",
"cui__regex-1.11.0",
"cui__semver-1.0.23",
"cui__serde-1.0.210",
"cui__serde_json-1.0.129",
"cui__serde_starlark-0.1.16",
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
"cui__sha2-0.10.8",
Added Rust 1.82.0 (#2944) https://blog.rust-lang.org/2024/10/17/Rust-1.82.0.html
2024-10-21 05:39:37 +00:00
"cui__spdx-0.10.6",
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
"cui__spectral-0.6.0",
Added Rust 1.82.0 (#2944) https://blog.rust-lang.org/2024/10/17/Rust-1.82.0.html
2024-10-21 05:39:37 +00:00
"cui__tempfile-3.13.0",
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
"cui__tera-1.19.1",
Added Rust 1.82.0 (#2944) https://blog.rust-lang.org/2024/10/17/Rust-1.82.0.html
2024-10-21 05:39:37 +00:00
"cui__textwrap-0.16.1",
"cui__toml-0.8.19",
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
"cui__tracing-0.1.40",
Added Rust 1.82.0 (#2944) https://blog.rust-lang.org/2024/10/17/Rust-1.82.0.html
2024-10-21 05:39:37 +00:00
"cui__tracing-subscriber-0.3.18",
Fix up fake resolve roots for proc macros (#2784) 1. Skip in-workspace proc-macros - they shouldn't be resolved, and are already resolve roots 2. Properly parse out git deps, rather than assuming everything is a registry dep Fixes #2777 Fixes #2783
2024-08-08 21:18:35 +00:00
"cui__url-2.5.2",
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
"generated_inputs_in_external_repo",
"libc",
"llvm-raw",
"rrra__anyhow-1.0.71",
"rrra__clap-4.3.11",
"rrra__env_logger-0.10.0",
"rrra__itertools-0.11.0",
"rrra__log-0.4.19",
"rrra__serde-1.0.171",
"rrra__serde_json-1.0.102",
Update bindgen version to 0.70.1 (#2872)
2024-09-18 16:01:06 +00:00
"rules_rust_bindgen__bindgen-0.70.1",
"rules_rust_bindgen__bindgen-cli-0.70.1",
"rules_rust_bindgen__clang-sys-1.8.1",
"rules_rust_bindgen__clap-4.5.17",
"rules_rust_bindgen__clap_complete-4.5.26",
"rules_rust_bindgen__env_logger-0.10.2",
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
"rules_rust_prost",
Update Prost (proto) dependencies to latest versions (#2810) This change also bumps the min tested Rust version to [Rust 1.72.1](https://github.com/rust-lang/rust/releases/tag/1.72.1) which is about a year old at this point.
2024-08-26 18:36:41 +00:00
"rules_rust_prost__h2-0.4.6",
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
"rules_rust_prost__heck",
Update Prost (proto) dependencies to latest versions (#2810) This change also bumps the min tested Rust version to [Rust 1.72.1](https://github.com/rust-lang/rust/releases/tag/1.72.1) which is about a year old at this point.
2024-08-26 18:36:41 +00:00
"rules_rust_prost__prost-0.13.1",
"rules_rust_prost__prost-types-0.13.1",
"rules_rust_prost__protoc-gen-prost-0.4.0",
"rules_rust_prost__protoc-gen-tonic-0.4.1",
"rules_rust_prost__tokio-1.39.3",
"rules_rust_prost__tokio-stream-0.1.15",
"rules_rust_prost__tonic-0.12.1",
Support building more things with bzlmod (#2601) This allows us to build more things with bzlmod with `WORKSPACE.bazel` disabled. This is required because when you use it as a module, it can't load dependencies from `WORKSPACE.bazel`. `bazel build --enable_bzlmod --noenable_workspace --lockfile_mode=off //... --keep_going` Before: Analysis succeeded for 937 of 978 top-level targets After: Analysis succeeded for 978 of 982 top-level targets Once we get those remaining targets working, we can then change our CI to add `--noenable_workspace` to our bzlmod configuration.
2024-04-03 15:38:38 +00:00
"rules_rust_proto__grpc-0.6.2",
"rules_rust_proto__grpc-compiler-0.6.2",
"rules_rust_proto__log-0.4.17",
"rules_rust_proto__protobuf-2.8.2",
"rules_rust_proto__protobuf-codegen-2.8.2",
"rules_rust_proto__tls-api-0.1.22",
"rules_rust_proto__tls-api-stub-0.1.22",
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
"rules_rust_test_load_arbitrary_tool",
Support bzlmod (#1528) This makes rules_rust load dependencies via bzlmod. Currently only basic functionality is completed, such as registering rustc toolchains and compiling crates. Note that it cannot interact with cargo, wasm or load any other rust toolchains such as rustfmt. There is one new module, `examples/bzlmod/hello_world`, that depends on the root `rules_rust` module. This example can be built and run using: ``` cd examples/bzlmod/hello_world bazel run //:hello_world ``` To register toolchains in an ergonomic way, it defines a new "hub" repository that contains all the toolchain proxies, so they can all be registered like so: ``` register_toolchains("@rust_toolchains//:all") ``` closes https://github.com/bazelbuild/rules_rust/issues/1493
2023-03-29 08:56:01 +00:00
"rules_rust_tinyjson",
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
"rules_rust_toolchain_test_target_json",
"rules_rust_wasm_bindgen__anyhow-1.0.71",
"rules_rust_wasm_bindgen__assert_cmd-1.0.8",
"rules_rust_wasm_bindgen__diff-0.1.13",
"rules_rust_wasm_bindgen__docopt-1.1.1",
"rules_rust_wasm_bindgen__env_logger-0.8.4",
"rules_rust_wasm_bindgen__log-0.4.19",
"rules_rust_wasm_bindgen__predicates-1.0.8",
"rules_rust_wasm_bindgen__rayon-1.7.0",
"rules_rust_wasm_bindgen__rouille-3.6.2",
"rules_rust_wasm_bindgen__serde-1.0.171",
"rules_rust_wasm_bindgen__serde_derive-1.0.171",
"rules_rust_wasm_bindgen__serde_json-1.0.102",
"rules_rust_wasm_bindgen__tempfile-3.6.0",
"rules_rust_wasm_bindgen__ureq-2.8.0",
Update wasm-bindgen to 0.2.89 (#2333) 0.2.88 was yanked. --------- Co-authored-by: UebelAndre <github@uebelandre.com>
2024-01-02 14:12:12 +00:00
"rules_rust_wasm_bindgen__walrus-0.20.3",
Update wasm-bindgen to 0.2.92 (#2714)
2024-06-24 20:33:21 +00:00
"rules_rust_wasm_bindgen__wasm-bindgen-0.2.92",
"rules_rust_wasm_bindgen__wasm-bindgen-cli-support-0.2.92",
"rules_rust_wasm_bindgen__wasm-bindgen-shared-0.2.92",
Allow additional targets to compile with bzlmod (#2314) See #2246 for how we declare dependencies automatically for third party crates. I'm using the same mechanism for all other repositories. Note that the MODULE.bazel changes in use_repo are autogenerated, and if you change the third party crates you depend on, you should get an error message saying something like "run this command to fix it" on your bzlmod presubmit environment.
2023-12-12 13:52:58 +00:00
"rules_rust_wasm_bindgen__wasmparser-0.102.0",
"rules_rust_wasm_bindgen__wasmprinter-0.2.60",
"rules_rust_wasm_bindgen_cli",
Support bzlmod (#1528) This makes rules_rust load dependencies via bzlmod. Currently only basic functionality is completed, such as registering rustc toolchains and compiling crates. Note that it cannot interact with cargo, wasm or load any other rust toolchains such as rustfmt. There is one new module, `examples/bzlmod/hello_world`, that depends on the root `rules_rust` module. This example can be built and run using: ``` cd examples/bzlmod/hello_world bazel run //:hello_world ``` To register toolchains in an ergonomic way, it defines a new "hub" repository that contains all the toolchain proxies, so they can all be registered like so: ``` register_toolchains("@rust_toolchains//:all") ``` closes https://github.com/bazelbuild/rules_rust/issues/1493
2023-03-29 08:56:01 +00:00
)
Support cargo_bazel_bootstrap for bzlmod (#2021) I've pulled out some of the code from https://github.com/bazelbuild/rules_rust/pull/1910 into a seperate PR, to simplify the review process. --------- Co-authored-by: scentini <rosica@google.com>
2023-10-25 14:23:31 +00:00
rust = use_extension("//rust:extensions.bzl", "rust")
rust.toolchain(edition = "2021")
use_repo(rust, "rust_toolchains")
register_toolchains(
"@rust_toolchains//:all",
)
Support building more things with bzlmod (#2601) This allows us to build more things with bzlmod with `WORKSPACE.bazel` disabled. This is required because when you use it as a module, it can't load dependencies from `WORKSPACE.bazel`. `bazel build --enable_bzlmod --noenable_workspace --lockfile_mode=off //... --keep_going` Before: Analysis succeeded for 937 of 978 top-level targets After: Analysis succeeded for 978 of 982 top-level targets Once we get those remaining targets working, we can then change our CI to add `--noenable_workspace` to our bzlmod configuration.
2024-04-03 15:38:38 +00:00
register_toolchains(
"//proto/protobuf:default-proto-toolchain",
)
register_toolchains(
"//proto/prost:default_prost_toolchain",
)
register_toolchains(
"//bindgen:default_bindgen_toolchain",
)
Make bazel lock file cross-platform (#2453) Since the host tools are os and arch specific, previously bazel would cache the resolution of these in the lock file, causing the repo for the wrong OS or arch to be used when moving between machines. Since bazel 7.1.0, module extensions can be marked as reproducible to exclude these from the lock file. However, the `rust` module extension handles fetching of all the other toolchains as well as the host tools, and we don't really want to exclude those too. Therefore the host tools are moved to their own module extension. This means we can no longer match the host toolchain's version, edition, etc with the toolchain registered via `rust.toolchain` by default, and instead default to a fixed version. This can still be overridden separately in the root module. I think this is okay, because the host tools are only used for bootstrapping and I don't think there's much need to have them match. This is tested by now checking in the MODULE.bazel.lock file of the bzlmod example, and running the bzlmod examples on multiple platforms with `--lockfile_mode` set to `error`. Resolves #2452 Resolves #2549
2024-04-05 09:58:07 +00:00
rust_host_tools = use_extension("//rust:extensions.bzl", "rust_host_tools")
use_repo(rust_host_tools, "rust_host_tools")
Support cargo_bazel_bootstrap for bzlmod (#2021) I've pulled out some of the code from https://github.com/bazelbuild/rules_rust/pull/1910 into a seperate PR, to simplify the review process. --------- Co-authored-by: scentini <rosica@google.com>
2023-10-25 14:23:31 +00:00
cargo_bazel_bootstrap = use_extension("//crate_universe/private/module_extensions:cargo_bazel_bootstrap.bzl", "cargo_bazel_bootstrap")
use_repo(cargo_bazel_bootstrap, "cargo_bazel_bootstrap")