| commit | 1be1d4aa361a6310e0ecd50a7c83311fdd48a1c5 | [log] [tgz] |
|---|---|---|
| author | George Burgess IV <gbiv@google.com> | Wed Mar 02 13:06:22 2022 -0800 |
| committer | George Burgess <gbiv@chromium.org> | Wed Mar 23 17:23:07 2022 +0000 |
| tree | cf4079c7b178669962c0418a71c245c22a591999 | |
| parent | e203161e48ec36c0abe885474eb2ac17abe874a3 [diff] |
toolchain: unify all rules Now that rules are parameterized consistently, we can tweak them a bit and have a centeralized list of all of the toolchain configurations we support. BUG=b:220355021 TEST=bazel-5 build ... Change-Id: If77ecc8e466174a8e122ce4febe4cb0b3335ac13 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/rules_cros/+/3503957 Reviewed-by: Chris McDonald <cjmcdonald@chromium.org> Tested-by: George Burgess <gbiv@chromium.org>
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 :)