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.

Sign up for GitHub

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

Jump to bottom

Allow specifying dependencies for individual artifacts #2887

Closed
wants to merge 9 commits into from
Closed

Allow specifying dependencies for individual artifacts #2887

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
69da8a8
Initial draft of artifact-specific dependencies RFC
dmarcuse Mar 24, 2019
57de202
Next draft of artifact-specific-dependencies RFC
dmarcuse Mar 23, 2020
81ae7b6
Add example with non-inline table
dmarcuse Mar 23, 2020
ec8e6fd
Add RFC PR link
dmarcuse Mar 23, 2020
db693e3
Use array-of-tables subtable TOML syntax
dmarcuse Mar 23, 2020
7de23cb
Add swift to prior art section and add links
dmarcuse Mar 27, 2020
dcc1cbd
Add clarification about duplicate dependency/dependency name checks
dmarcuse Mar 27, 2020
55ef3d2
Reword some slightly redundant phrasing
dmarcuse Mar 27, 2020
a5aef08
Remove some redundant lines
dmarcuse Mar 28, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Add swift to prior art section and add links
  • Loading branch information
@dmarcuse
dmarcuse committed Mar 27, 2020
commit 7de23cb5d96d3a90ddd4885346e37e46c100cc8f
5 changes: 3 additions & 2 deletions text/0000-cargo-artifact-specific-dependencies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,8 +104,9 @@ Specifically for test/bench/example artifacts, the `dev-dependencies` section ma
# Prior art
[prior-art]: #prior-art

- CMake allows, and in fact, recommends, specifying library dependencies that only apply to a specific build artifact through its `target_link_libraries` command
- Gradle allows different build artifacts to use different source sets/dependency configurations
- CMake allows, and in fact, recommends, specifying library dependencies that only apply to a specific build artifact through its `target_link_libraries` command [(Source)](https://cmake.org/cmake/help/latest/command/target_link_libraries.html)
- Swift is implementing functionality to specify dependencies per-target by specifying dependencies in the package manifest and then enabling them for targets as necessary [(Source)](https://github.com/apple/swift-evolution/blob/master/proposals/0226-package-manager-target-based-dep-resolution.md)
- Gradle allows different build artifacts to use different source sets/dependency configurations (this is less directly comparable due to the way Java loads libraries at runtime)

# Unresolved questions
[unresolved-questions]: #unresolved-questions
Expand Down