-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Passing non-boolean options to dependencies #1315
Comments
There are indeed! All enabled features of a crate are passed through into the build script. This means various options are enabled via enabling features. |
@alexcrichton This is not really what I'm looking for. This only allows me to set on/off flags, which represent packages. I want to be able to set other options, like integers, version numbers, etc. |
Ah yes, this is not currently supported (you'd have to add a feature-per-value basically). |
As there hasn't been any activity here in a while would someone (the author, a team member, or any interested party) be able to summarise the current state, perhaps making explicit:
Thank you! (The cargo team is currently evaluating the use of Stale bot, and using #6035 as the tracking issue to gather feedback.) If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable! |
As I didn't see any updates in 30 days I'm going to close this. Please see the previous comment for more information! |
Is it possible to pass options to the build script of one of the dependencies? I require this for some sophisticated code generation.
The text was updated successfully, but these errors were encountered: