diff options
author | Kristina Chodorow <kchodorow@google.com> | 2015-04-06 20:33:09 +0000 |
---|---|---|
committer | Damien Martin-Guillerez <dmarting@google.com> | 2015-04-08 08:45:45 +0000 |
commit | be1a1053ab822ec731a36a8a7ec000fb809a8a2d (patch) | |
tree | accfd602e27c466a56e66038118d3540565c6bb0 /site/blog/_posts | |
parent | 2af9425de94154720129f8061c9fd7061c3a65b4 (diff) |
Add a blog post about simplified workspace creation
--
MOS_MIGRATED_REVID=90442814
Diffstat (limited to 'site/blog/_posts')
-rw-r--r-- | site/blog/_posts/2015-04-06-Simplified-Workspace-Creation.md | 36 |
1 files changed, 36 insertions, 0 deletions
diff --git a/site/blog/_posts/2015-04-06-Simplified-Workspace-Creation.md b/site/blog/_posts/2015-04-06-Simplified-Workspace-Creation.md new file mode 100644 index 0000000000..334d06f240 --- /dev/null +++ b/site/blog/_posts/2015-04-06-Simplified-Workspace-Creation.md @@ -0,0 +1,36 @@ +--- +layout: posts +title: Announcing simplified workspace creation +--- + +To create a new workspace, you can now simply create an empty `WORKSPACE` file +in a directory. + +Previously, you'd need to copy or symlink the `tools` directory into your +project, which was unpopular: + +!["move my-project/ to be a subdirectory of base_workspace/" Ok. Ctrl-W.]({{ site_root }}/assets/ctrl-w-tweet.png) + +[Miguel Alcon](https://github.com/mikelalcon) came up with a great idea for +making this process simpler. Now the `compile.sh` script will create a +`.bazelrc` file in your home directory which tells Bazel where `compile.sh` was +run from and, thus, where it can find its tools when you build. + +To use this new functionality, get the latest version of the code from Github, +run `./compile.sh`, and then create a Bazel workspace by running +`touch WORKSPACE` in any directory. + +Some caveats to watch out for: + +* If you move the directory where Bazel was built you will need to +update your `~/.bazelrc` file. +* If you would like to use different tools than the ones `compile.sh` +finds/generates, you can create a `tools/` directory in your project and +Bazel will attempt to use that instead of the system-wide one. + +See the [getting started]({{ site_root }}/docs/getting-started.html) docs for more info about +setting up your workspace. + +Let us know if you have any questions or issues on the +[mailing list](groups.google.com/forum/#!forum/bazel-discuss) or +[GitHub](https://github.com/google/bazel). |