-
Notifications
You must be signed in to change notification settings - Fork 105
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
Fix features selection, broken by #478 #524
Conversation
Currently many things fail to build due to google#478 stripping out all the features.
It works properly with no explicit targets set (aka "use all the targets"), and it also works properly with some of the examples that set `default-members = []`. I think there's still something wrong, because it dropped features from some Windows-specific crates relative to before google#478, but I'm not sure what's supposed to happen. At least all the tests in this repository pass on Linux again...
@sayrer FYI, if you want to take a look. |
It doesn't work any more, now that I changed the code to only use supported targets.
This is how I work around rust-lang/cargo#5042 to get path dependencies into vendored Rust dependencies. The generated BUILD files are built with google#524, because otherwise they don't work. This fixes google#361.
Latest rules_rust now requires them. Can't use the 0.16 release due to not-yet-merged google/cargo-raze#524
I believe this fixes the issue outlined in #530. Thanks a bunch for working on this and fixing it! |
@dfreese is there any chance this change could be included in a patch/minor release? If this fixes the issue, it would be a huge unblocker for our repo |
@dfreese @illicitonion @acmcarther could one of you review this and release v0.16.1? |
@sayrer Please could you give this a look? |
published 0.16.1 |
It works properly with no explicit targets set (aka "use all the
targets"), and it also works properly with some of the examples that set
default-members = []
.I think there's still something wrong, because it dropped features from
some Windows-specific crates relative to before #478, but I'm not sure
what's supposed to happen. At least all the tests in this repository
pass on Linux again...