Name | Date | Size | #Lines | LOC | ||
---|---|---|---|---|---|---|
.. | - | - | ||||
BUILD.bazel | H A D | 25-Apr-2025 | 369 | 21 | 17 | |
README.rst | H A D | 25-Apr-2025 | 444 | 11 | 8 | |
main.go | H A D | 25-Apr-2025 | 671 | 25 | 7 | |
name_test.sh | H A D | 25-Apr-2025 | 242 | 7 | 6 |
README.rst
1Executable name 2=============== 3 4.. _go_binary: /docs/go/core/rules.md#go_binary 5 6The filename of the executable produced by a go_binary_ rule is unpredictale, the full path includes 7the compilation mode amongst other things, and the rules offer no backwards compatibility guarantees 8about the filename. 9For the simple case where you know exactly what you want the output filename to be, you can use a 10genrule to copy it to a well known place. 11