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.
Small step toward #723 .
Introduces a few new cargo commands so that developers and the CI can easily run the same commands.
cargo build-all
==cargo build --workspace --all-targets
cargo build-wasm-tendermint
== (build tendermint with the wasm32-unknown-unknown target)cargo build-wasm-light-client
== (build tendermint-light-client with the wasm32-unknown-unknown target)This is a small example of how building and testing can be simplified between the developer and the CI. Further cases will come as I research the tools mentioned in #723.
Edit: it would be nice to have a simple
cargo build-wasm
command, but currently it's not possible, because the--no-default-features
parameter cannot run in a virtual workspace, hence we need to add the--manifest-path
parameter to point to the specific package'sCargo.toml
as well as the--package
parameter (describing the crate name) to point to the package that should be built.