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

Simplified Target-Specific Dependencies #1758

Closed
randomPoison opened this issue Jun 27, 2015 · 2 comments
Closed

Simplified Target-Specific Dependencies #1758

randomPoison opened this issue Jun 27, 2015 · 2 comments

Comments

@randomPoison
Copy link

As I understand it to specify target-specific dependencies you need to use the full target triple:

[target.x86_64-unknown-linux-gnu.dependencies]
openssl = "1.0.1"

[target.x86_64-pc-windows-gnu.dependencies]
winhttp = "0.4.0"

But a platform like Windows has multiple target triples and if I want to declare windows specific dependencies I have to repeat them across all of the target triples:

[target.i686-pc-windows-gnu.dependencies]
libc = "*"
winapi = "*"
ole32-sys = "*"

[target.x86_64-pc-windows-gnu.dependencies]
libc = "*"
winapi = "*"
ole32-sys = "*"

[target.x86_64-pc-windows-msvc.dependencies]
libc = "*"
winapi = "*"
ole32-sys = "*"

This quickly becomes tedious. I'd like a simplified version where I can specify a set of dependencies for a platform, something like [target.windows.dependencies]. The broader platform sets could match those used by the [cfg()] attribute (e.g. "windows", "unix", "macos", etc.).

Related to #1197 this could also be applied to features as [target.windows.features].

Thanks.

@alexcrichton
Copy link
Member

Dupe of #1007, but thanks for the report!

@randomPoison
Copy link
Author

Sorry about that! Must have missed it when looking over the existing issues.

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

No branches or pull requests

2 participants