diff --git a/docs/developers/best-practices/the-dynamic-allocation-problem.md b/docs/developers/best-practices/the-dynamic-allocation-problem.md index 15f97959..45aa3efc 100644 --- a/docs/developers/best-practices/the-dynamic-allocation-problem.md +++ b/docs/developers/best-practices/the-dynamic-allocation-problem.md @@ -65,5 +65,5 @@ Make sure you migrate to the managed types **incrementally** and **thoroughly te ::: :::tip -You can use the `mxpy contract report` command to verify whether your contract still requires dynamic allocation or not. +You can use the `sc-meta report` command to verify whether your contract still requires dynamic allocation or not. ::: diff --git a/docs/developers/meta/sc-build-reference.md b/docs/developers/meta/sc-build-reference.md index 337a3c3d..46aa1e03 100644 --- a/docs/developers/meta/sc-build-reference.md +++ b/docs/developers/meta/sc-build-reference.md @@ -7,18 +7,12 @@ title: Build Reference ## How to: Basic build -To build a contract, it is enough to navigate in your contract crate and run +To build a contract, navigate to the contract folder and run the following command: ```sh sc-meta all build ``` -:::info Note -The traditional way to trigger a build in console is to call `mxpy contract build --path `, which works as well. However, mxpy currently just forwards commands to the [MultiversX Metaprogramming standalone tool](/developers/meta/sc-meta#introduction), so you might as well call it directly. -::: - ---- - [comment]: # (mx-exclude-context) ## Configuring the build @@ -157,8 +151,6 @@ After building the contracts, there are three more operations left to perform, b Calling `cargo run clean` in the meta crate will run `cargo clean` in all wasm crates and delete the `output` folder. -`mxpy contract clean` also just forwards to this. - Note that even the clean operation relies on the ABI, in order to reach all the wasm crates. [comment]: # (mx-context-auto) diff --git a/docs/developers/meta/sc-meta-cli.md b/docs/developers/meta/sc-meta-cli.md index 0c4765e7..25032d6e 100644 --- a/docs/developers/meta/sc-meta-cli.md +++ b/docs/developers/meta/sc-meta-cli.md @@ -388,7 +388,7 @@ This command is similar to `build-dbg`, in that it provides a shorthand for buil ### Calling `clean` -Calling `mxpy contract clean ` or `cargo run clean` in the meta crate will delete the `output` folder and clean outputs of the Rust crates. +Calling `cargo run clean` in the meta crate will delete the `output` folder and clean outputs of the Rust crates. [comment]: # (mx-context-auto) @@ -419,4 +419,4 @@ Calling `cargo run cs` in the meta crate or `sc-meta cs` in the root crate will Subcommands: - `install` Pulls the latest chain simulator docker image available. This command needs Docker to be installed and running on the current machine. - `start` Starts the chain simulator in verbose mode at `localhost:8085`. -- `stop` Stops the chain simulator. \ No newline at end of file +- `stop` Stops the chain simulator.