I have a crate foo_sys
. In Rust 2015 I used extern crate foo_sys as foo
for convenience, but in Rust 2018 extern crate
isn't needed anymore and I don't want to use it only for aliasing. When dropping extern crate
, I get
error[E0463]: can't find crate for
foo
extern crate foo indicates that you want to link against an external library and brings the top-level crate name into scope (equivalent to use foo ). As of Rust 2018, in most cases you won't need to use extern crate anymore because Cargo informs the compiler about what crates are present. (
The crate root is a source file that the Rust compiler starts from and makes up the root module of your crate (we'll explain modules in depth in the “Defining Modules to Control Scope and Privacy” section). A package is a bundle of one or more crates that provides a set of functionality. A package contains a Cargo.
registry/src If a downloaded . crate archive is required by a package, it is unpacked into registry/src folder where rustc will find the . rs files.
This can be achieved with the rename-dependency Cargo feature, available in Rust 1.31. With this feature, it's possible to provide a package attribute to the dependencies:
The rename-dependency feature allows you to import a dependency with a different name from the source. This can be useful in a few scenarios:
- Depending on crates with the same name from different registries.
- Depending on multiple versions of a crate.
- Avoid needing
extern crate foo as bar
in Rust source.
Instead of writing
[dependencies]
foo_sys = "0.2"
the package
key can be added to the dependency in Cargo.toml
:
[dependencies]
foo = { package = "foo_sys", version = "0.2" }
WARNING: Cargo prior to Rust 1.26.0 may download the wrong dependency when using this feature!
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With