| commit | bad49c4a1139afdb257fed0af6bd1dc20a6c21a1 | [log] [tgz] |
|---|---|---|
| author | Felipe de A. Mello Pereira <felipeamp@google.com> | Thu Sep 12 15:16:37 2024 +0200 |
| committer | GitHub <noreply@github.com> | Thu Sep 12 13:16:37 2024 +0000 |
| tree | 19b220e8158d8ea0212dc3a9d219e2c84d977903 | |
| parent | 5063cd8096432a1eae68c70b4c6139ab1b9f8785 [diff] |
Build `rust_test` targets using a crate name different from the underlying lib (#2828) This is a rollforward of https://github.com/bazelbuild/rules_rust/pull/2803, but behind the `incompatible_change_rust_test_compilation_output_directory` incompatible flag. This PR also makes `rust_test` put its compilation outputs in the same directory as the `rust_library` rule (i.e. not in a `test-{hash}` subdirectory anymore). After this change both the `rust_library` and `rust_test` rules will put all its compilation outputs in the same directory, but there won't be any name collisions in non-sandboxed environments (see https://github.com/bazelbuild/rules_rust/pull/1427 for more context). Issue with context: https://github.com/bazelbuild/rules_rust/issues/2827
This repository provides rules for building Rust projects with Bazel.
General discussions and announcements take place in the GitHub Discussions, but there are additional places where community members gather to discuss rules_rust.
Please refer to the full documentation.