We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
cargo check
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
Looks like if there's a binary target then the libraries are compiled entirely instead of only requiring metadata.
I ran cargo new foo followed by touch src/main.rs, and also added a dependency on libc from crates.io. After that a cargo check -v yielded:
cargo new foo
touch src/main.rs
libc
cargo check -v
Running `rustc --crate-name libc /.../src/lib.rs --crate-type metadata ` Running `rustc --crate-name libc /.../src/lib.rs --crate-type lib ` Running `rustc --crate-name foo src/lib.rs --crate-type metadata ` Running `rustc --crate-name foo src/lib.rs --crate-type lib ...` Running `rustc --crate-name foo src/main.rs --crate-type metadata ...`
The text was updated successfully, but these errors were encountered:
@nrc could you help look into this?
Sorry, something went wrong.
02625ba
No branches or pull requests
Looks like if there's a binary target then the libraries are compiled entirely instead of only requiring metadata.
I ran
cargo new foo
followed bytouch src/main.rs
, and also added a dependency onlibc
from crates.io. After that acargo check -v
yielded:The text was updated successfully, but these errors were encountered: