| commit | 187e80dd6ac02bc1372d26178bbbebb518c6bad0 | [log] [tgz] |
|---|---|---|
| author | Chris McDonald <cjmcdonald@chromium.org> | Thu Feb 03 14:52:30 2022 -0700 |
| committer | Chris McDonald <cjmcdonald@chromium.org> | Thu Feb 03 21:54:41 2022 +0000 |
| tree | b293f4869740f22d3ffcd8dcf33edceb10eecb57 | |
| parent | 730f3f9889fdb87ac9f9eef3cec57730eb31be9e [diff] |
bazelrc: Enable experimental_platform_in_output_dir With Bazel 5 available we can now enable this experimental flag. This behavior is desirable to allow switching between platform targets without clobbering the existing bazel-out/ directory and throwing away work. BUG=b:213616502 TEST=local drydock build Change-Id: Idadaf284ed211fbe1d271512035d4a3fff75cd57 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/rules_cros/+/3437430
This repository provides common rules and configuration for Bazel projects in Chrome OS.
rules_cros is only expected to function inside the Chrome OS SDK. You may copy the following snippet into your WORKSPACE file and fix up the relative path in local_repository to point from your project to where rules_cros is checked out.
local_repository( name = "rules_cros", path = "../src/platform/rules_cros", ) load("@rules_cros//cros:repositories.bzl", "rules_cros_dependencies") rules_cros_dependencies()
You will also need to symlink .bazelrc in the root of your project to common.bazelrc in this repo. You can put additional settings in a file named user.bazelrc in the root of your WORKSPACE and it will automatically be imported by common.bazelrc.
The code is this directory is experimental and under active development. Stability and functionality is not guaranteed :)