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

Update crate_universe to determine dep+feature trees per host #2877

Merged
merged 7 commits into from
Sep 18, 2024

Conversation

UebelAndre
Copy link
Collaborator

@UebelAndre UebelAndre commented Sep 17, 2024

This change expands the use of cargo tree to resolve features for different combinations of host -> target platform triples where before cargo-bazel was only capable of resolving host dependencies for the current host platform and not a foreign platform.

A lengthy description of how this was done can be found at crate_universe/src/metadata/cargo_tree_resolver.rs - TreeResolver::create_rustc_wrapper.

closes #2212

Copy link
Collaborator

@illicitonion illicitonion left a comment

Choose a reason for hiding this comment

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

Fancy! Exciting! Only slightly terrifying!

Just one docs question really :)

crate_universe/src/metadata/cargo_tree_resolver.rs Outdated Show resolved Hide resolved
crate_universe/src/metadata/cargo_tree_resolver.rs Outdated Show resolved Hide resolved
UebelAndre and others added 2 commits September 18, 2024 04:28
Co-authored-by: Daniel Wagner-Hall <dawagner@gmail.com>
Copy link
Collaborator

@illicitonion illicitonion left a comment

Choose a reason for hiding this comment

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

Looks great! Thanks!

@UebelAndre UebelAndre added this pull request to the merge queue Sep 18, 2024
Merged via the queue into bazelbuild:main with commit 350d249 Sep 18, 2024
4 checks passed
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.

Inconsistent cargo bazel lockfile between MacOS and Linux
2 participants