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

Build rust_test targets using a crate name different from the underlying lib #2828

Commits on Sep 2, 2024

  1. Build rust_test targets using a crate name different from the

    underlying lib
    
    This is a rollforward of
    bazelbuild#2803, but behind a feature
    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
    bazelbuild#1427 for more context).
    
    Issue: bazelbuild#2827
    felipeamp committed Sep 2, 2024
    Configuration menu
    Copy the full SHA
    a99f026 View commit details
    Browse the repository at this point in the history

Commits on Sep 11, 2024

  1. Configuration menu
    Copy the full SHA
    0656abd View commit details
    Browse the repository at this point in the history

Commits on Sep 12, 2024

  1. Merge remote-tracking branch 'felipeamp/main' into add-feature-flag-a…

    …nd-change-rust-test-compilation-output-dir
    felipeamp committed Sep 12, 2024
    Configuration menu
    Copy the full SHA
    3986b3b View commit details
    Browse the repository at this point in the history