blob: 334d06f2408c550ba20811e2843851f5a7f9cd42 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
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:
[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).
|
