Tracking Issue for RFC 3028: Allow "artifact dependencies" on bin, cdylib, and staticlib crates · Issue #9096 · rust-lang/cargo (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Description

Summary

RFC: #3028
Related Issues: #4316
Implementation: #9992
Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#artifact-dependencies
Issues: Z-bindeps Nightly: binary artifact dependencies

Allow Cargo packages to depend on bin, cdylib, and staticlib crates, and use the artifacts built by those crates.

Unresolved issues

• Make a list of any known implementation or design issues.
• Add support for inheriting the source of an artifact dependency
• Ensure we have a test for an artifact dep on a bin with required-features without specifying the features; ensure the behavior is reasonable
• cargo tree support: Display artifact dependency information in cargo tree #14804

Notes

• Once implemented, reopen Cargo: providing artifacts (for artifact dependencies) via build.rs rfcs#3035
• When stabilizing, be sure to update INDEX_V_MAX.

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.