chore: migrate target/artifacts to release_artifacts to avoid cargo clean loss #374
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.
in order to avoid glibc errors when compiling, it is necessary to run cargo clean prior to cross build as per solution 2 in this cross-rs issue
In doing so, it deletes the created
target/artifacts
folder.We can either
target/artifacts
foldercargo clean -p <libname> --release
which should in theory only delete the release artifacts for a particular target but I've not tested out if this worksI've elected for option 1