-
Notifications
You must be signed in to change notification settings - Fork 402
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
What's the best way to vary crate_features? #801
Comments
I got this to sort of work:
|
Would #566 give you what you're looking for? |
I don't think so, but would be happy to be corrected. If I use the functions like Frustratingly, none of the examples that read these flags do anything other than print them, like this one. |
I think the problem with #566 is that those arguments will get passed to every crate, but what I really want to do is enable features in specific crates, and |
I think this would work if
|
I think it'd be reasonable to call expand_locations on |
With my patch, I'm able to do something like this: rules.bzl:
BUILD.bazel:
simple.rs:
That way, I can set things on specific targets, not just globally. Note that "bar" is on by default. Here's the output:
|
Fixed by #809. |
Expand locations in rustc_flags. Fixes #801.
Suppose I want to change
crate_features
arguments on thebazel
command line. What's the best way?The text was updated successfully, but these errors were encountered: