From f2b12756ee784c23d6961c1308634a95514b0cb0 Mon Sep 17 00:00:00 2001 From: Roman Khimov Date: Thu, 28 Jan 2021 12:14:50 +0300 Subject: [PATCH] docs: use contract instead of mycontract throughout the compiler doc --- docs/compiler.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/compiler.md b/docs/compiler.md index 236a77746..1eb2adaa8 100644 --- a/docs/compiler.md +++ b/docs/compiler.md @@ -54,13 +54,13 @@ export GOROOT=/usr/lib64/go/1.14 ### Compiling ``` -./bin/neo-go contract compile -i mycontract.go +./bin/neo-go contract compile -i contract.go ``` By default the filename will be the name of your .go file with the .nef extension, the file will be located in the same directory where your Go contract is. If you want another location for your compiled contract: ``` -./bin/neo-go contract compile -i mycontract.go --out /Users/foo/bar/contract.nef +./bin/neo-go contract compile -i contract.go --out /Users/foo/bar/contract.nef ``` If you contract is split across multiple files, you must provide a path @@ -74,7 +74,7 @@ to the directory where package files are contained instead of a single Go file You can dump the opcodes generated by the compiler with the following command: ``` -./bin/neo-go contract inspect -i mycontract.go -c +./bin/neo-go contract inspect -i contract.go -c ``` This will result in something like this: @@ -156,7 +156,7 @@ manifest generated by the compiler from configuration file provided in YAML format. To create contract manifest pass YAML file with `-c` parameter and specify manifest output file with `-m`: ``` -./bin/neo-go contract compile -i mycontract.go -c myconfig.yml -m mycontract.manifest.json +./bin/neo-go contract compile -i contract.go -c config.yml -m contract.manifest.json ``` Example YAML file contents: