aboutsummaryrefslogtreecommitdiffhomepage
path: root/site
diff options
context:
space:
mode:
authorGravatar Ittai Zeidman <ittaiz@gmail.com>2016-07-14 14:28:19 +0000
committerGravatar Yue Gan <yueg@google.com>2016-07-14 17:45:55 +0000
commit26ba23e465aad365138006b906431a865c5766cc (patch)
tree1a094168ac61c2b0d47b11e707f2eb1857c28144 /site
parentaa0940a4de414dee547e4ce2e0a1e95c26393021 (diff)
clarified needing to run generate_workspace from bazel source folder
Hi, If you feel this is unnecessary please feel free to close this PR but it took me some time and @lberki's help to understand that even though I built the binary from source and I have the source cloned then I still need to run the command from the source folder so I added that note in. Closes #1489. -- Reviewed-on: https://github.com/bazelbuild/bazel/pull/1489 MOS_MIGRATED_REVID=127429574
Diffstat (limited to 'site')
-rw-r--r--site/docs/external.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/site/docs/external.md b/site/docs/external.md
index f1ef7c4542..1bcdc683d7 100644
--- a/site/docs/external.md
+++ b/site/docs/external.md
@@ -62,6 +62,8 @@ following to build the tool and see usage:
bazel run //src/tools/generate_workspace
```
+Note that you need run this from your Bazel source folder even if you build your binary from source.
+
You can specify directories containing Bazel projects (i.e., directories
containing a `WORKSPACE` file), Maven projects (i.e., directories containing a
`pom.xml` file), or Maven artifact coordinates directly. For example: