refactor: Use cargo-near to build project #275
Merged
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
|
@ghimire007 I cleaned up the code even further. This PR is only waiting for a new cargo-near release (crates with |
|
@frol I have updated project to use cargo-near 0.3.1 |
…naries compiled with Rust 1.70.0
frol
approved these changes
Jun 26, 2023
Comment on lines
+18
to
+22
| release: true, | ||
| embed_abi: true, | ||
| doc: false, | ||
| color: cargo_near::ColorPreference::Always, | ||
| no_abi: true, |
There was a problem hiding this comment.
Just for future context, there was no analysis on which flags actually make sense to use, so we just followed the existing setup - a simple release-mode build for wasm target.
frol
changed the title
Merged
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.
replaced existing build logic to use cargo near to resolve #230