milarin/gocc
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 3 Wiki Activity

updated README

Browse Source
This commit is contained in:
Timon Ringwald 2022-08-18 15:06:39 +02:00
parent 9569739605
commit bd0ed87f70
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -59,24 +59,28 @@ Usage of ./gocc:
By default, `gocc` compiles the module in the current working directory. By default, `gocc` compiles the module in the current working directory.
You can provide a custom module path after all other arguments. You can provide a custom module path after all other arguments.
For example: `gocc -t 4 -ignoreconfig path/to/go/module` Example: `gocc -t 4 -ignoreconfig path/to/go/module`
#### Choosing Operating systems #### Choosing Operating systems
You can decide, for which operating systems `gocc` should compile for via `-os`. You can decide, for which operating systems `gocc` should compile for via `-os`.
Provide the operating systems as a comma-separated list. Provide the operating systems as a comma-separated list.
For example: `gocc -os "windows,linux"` Example: `gocc -os "windows,linux"`
For a list of supported operating systems, run `go tool dist list` For a list of supported operating systems, run `go tool dist list`.
Providing no `-os` flag will compile for all available systems (without config file)
#### Choosing architectures #### Choosing architectures
Analogous to operating systems, you can provide architectures via `-arch`. Analogous to operating systems, you can provide architectures via `-arch`.
For example: `gocc -arch "amd64,386"` Example: `gocc -arch "amd64,386"`
For a list of supported architectures, run `go tool dist list` For a list of supported architectures, run `go tool dist list`.
Providing no `-arch` flag will compile for all available architectures (without config file)
#### Output path #### Output path