Publish as a Cargo package with explicit binary and library targets #19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
timrogers
force-pushed
the
timrogers/crate
branch
from
dabfc20 to
a5d40f7
Compare
This was referenced Feb 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following @Holzhaus's great feedback in #16 and initial implementation in #17, this configures the project so that it can be published as a Cargo package on Crates.io.
The Cargo package exposes a binary target, which can be easily installed with
cargo install litra, plus a library target which can be used to integrate Litra control into other Rust applications.The package will be automatically published to Crates.io when a release is created.