aboutsummaryrefslogtreecommitdiff
path: root/tests/examples/executable_name/README.rst
diff options
context:
space:
mode:
Diffstat (limited to 'tests/examples/executable_name/README.rst')
-rw-r--r--tests/examples/executable_name/README.rst10
1 files changed, 10 insertions, 0 deletions
diff --git a/tests/examples/executable_name/README.rst b/tests/examples/executable_name/README.rst
new file mode 100644
index 00000000..4db0db04
--- /dev/null
+++ b/tests/examples/executable_name/README.rst
@@ -0,0 +1,10 @@
+Executable name
+===============
+
+.. _go_binary: /docs/go/core/rules.md#go_binary
+
+The filename of the executable produced by a go_binary_ rule is unpredictale, the full path includes
+the compilation mode amongst other things, and the rules offer no backwards compatibility guarantees
+about the filename.
+For the simple case where you know exactly what you want the output filename to be, you can use a
+genrule to copy it to a well known place.