fix: include memory layout files in metapac package - #44
Merged
Conversation
This file contains hidden or 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
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.
This fixes the generated
ch32-metapacpackage include list for the new runtime memory layout files introduced by Rich Memory Layout (#36).cargo publish --dry-run --features ch32v003f4u6currently fails after copying README/LICENSE because the crate tarball excludessrc/chips/**/memory_x/**, sobuild.rscannot readmemory_x/_defaultfrom the packaged crate. README and license files are also referenced by the manifest/publish metadata, so include them explicitly.@aq1018 FYI, this is the packaging follow-up for the memory layout work. After this lands, we plan to regenerate/push
ch32-metapacand publishch32-metapac 0.1.0to crates.io.Verification:
The dry run packages 803 files and verifies
ch32-metapac v0.1.0successfully.