You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
cargo check cannot be used directly in a multi-target crate, one has to state which target to build (the library or a selected binary).
Fixing this could get a bit tedious since selecting a target binary will be project specific, not a general option for the linter. But targeting the library can be a global option. Therefore I propose to add another command to the drop-down menu dubbed check --lib, which invokes cargo check --lib.
This way people can at least build the library in a multi-target crate for now.
The text was updated successfully, but these errors were encountered:
cargo check
cannot be used directly in a multi-target crate, one has to state which target to build (the library or a selected binary).Fixing this could get a bit tedious since selecting a target binary will be project specific, not a general option for the linter. But targeting the library can be a global option. Therefore I propose to add another command to the drop-down menu dubbed
check --lib
, which invokescargo check --lib
.This way people can at least build the library in a multi-target crate for now.
The text was updated successfully, but these errors were encountered: