Lines Matching +full:- +full:- +full:workspace

26 ## Set up a Bazel workspace
29 [Bazel workspace](https://docs.bazel.build/versions/master/build-ref.html#workspace)
31 software you want to build. Each workspace directory has a text file named
32 `WORKSPACE` which may be empty, or may contain references to external
35 First, create a directory for your workspace:
41 Next, you’ll create the `WORKSPACE` file to specify dependencies. A common and
46 To do this, in the root directory of your workspace (`my_workspace/`), create a
47 file named `WORKSPACE` with the following contents:
55   strip_prefix = "googletest-609281088cfefc76f9d0ce82e1ff6c30cc3591e5",
67 code, so add the following to the `WORKSPACE` file:
73   strip_prefix = "rules_cc-40548a2974f1aea06215272d9c2b47a14a24e556",
81 With your Bazel workspace set up, you can now use GoogleTest code within your
118 GoogleTest (`//:gtest_main`) using the prefix you specified in the `WORKSPACE`
126 <strong>my_workspace$ bazel test --test_output=all //:hello_test</strong>
133 [----------] Global test environment set-up.
134 [----------] 1 test from HelloTest
137 [----------] 1 test from HelloTest (0 ms total)
139 [----------] Global test environment tear-down
143 Target //:hello_test up-to-date:
144   bazel-bin/hello_test
146 INFO: 27 processes: 8 internal, 19 linux-sandbox.