Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

cargo-check cannot be used with multi-target crate #61

Open
W4RH4WK opened this issue Aug 10, 2016 · 1 comment · May be fixed by #169
Open

cargo-check cannot be used with multi-target crate #61

W4RH4WK opened this issue Aug 10, 2016 · 1 comment · May be fixed by #169

Comments

@W4RH4WK
Copy link

W4RH4WK commented Aug 10, 2016

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.

@colin-kiegel
Copy link
Contributor

link to the upstream issue rsolomo/cargo-check#4

@QuantumEntangledAndy QuantumEntangledAndy linked a pull request Aug 3, 2021 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants