We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Cargo.lock is normally included for projects with a binary. By the way, it's ignored when building as library dependency.
The text was updated successfully, but these errors were encountered:
Dupe of #10
Sorry, something went wrong.
May I continue the discussion here? All projects contains more than one binary, independent of the usecase, should have a lockfile.
http://doc.crates.io/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
No, you mayn't. The executable is a usage example. EOT
No branches or pull requests
Cargo.lock is normally included for projects with a binary. By the way, it's ignored when building as library dependency.
The text was updated successfully, but these errors were encountered: