From 26ba23e465aad365138006b906431a865c5766cc Mon Sep 17 00:00:00 2001 From: Ittai Zeidman Date: Thu, 14 Jul 2016 14:28:19 +0000 Subject: 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 --- site/docs/external.md | 2 ++ 1 file changed, 2 insertions(+) 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: -- cgit v1.2.3