-
Notifications
You must be signed in to change notification settings - Fork 252
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
Add support for cargo feature flags #60
Comments
Hey @hobofan, thanks for opening this issue. I think this is a solid idea. My initial thought is that adding the following flags should do the trick: Anyway, @hobofan are you interested in hacking on this? I'm happy to help in whatever way. |
Hey @hobofan just wanted to follow-up on this. Once #73 lands, we will have a pretty solid way to handle this. A little background, the idea with #73 is that we will be able to declare more specific details on the Rust project to be compile like so: To address the feature requests you've mentioned here, we can add a new It will be super easy to implement this feature and any other like it. I'll keep this issue up-to-date. Once #73 lands (the 0.7.0 release), would you be interested in getting your feet wet and adding this functionality? |
Well @thedodd, after submitting #160, I think I might give this one a go as well. I've opened a PR, see #183. I expect this to be done in the next 1-4 days. |
I think my PR #183 should close this issue. |
I need to pass |
Any updates on this? |
@janhohenheim I'm working on merging the changes into my PR. Thanks for reminding me 👍 See #183 for details. |
It would be great to have the ability to specify cargo feature flags for the internal invocation of
cargo build
.Maybe it would even make more sense to make this even more generic and pass any number of arguments to the cargo invocation, as this would also cover other flags like "--no-default-features" etc., which otherwise have to be manually mirrored.
The text was updated successfully, but these errors were encountered: