TrueCloudLab/neoneo-go
7
0
Fork 2
Code Issues Pull requests Projects Releases Packages Wiki Activity

docs: use contract instead of mycontract throughout the compiler doc

Browse source
This commit is contained in:
Roman Khimov 2021-01-28 12:14:50 +03:00
parent a217d62f8a
commit f2b12756ee
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/compiler.md
View file

@ -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: