| commit | 6453254e30abbf772ca2d8a8a4e337489229dc35 | [log] [tgz] |
|---|---|---|
| author | George Burgess IV <gbiv@google.com> | Mon Mar 14 15:53:32 2022 -0700 |
| committer | George Burgess <gbiv@chromium.org> | Wed Mar 23 17:23:07 2022 +0000 |
| tree | b4bb663aae86e16f454c87062faa19701e2b8503 | |
| parent | 1be1d4aa361a6310e0ecd50a7c83311fdd48a1c5 [diff] |
emulation: parameterize Parameterize all of the emulation-side rules, so they're easier to generate from a unified set of toolchain attributes in a later patch. (This happens after the 'unify' commit because I already wrote it in its fully unified form.) BUG=b:220355021 TEST=bazel-5 build ... Change-Id: I9f737b24fd27d183a8a8b17ea3e14d919132c36e Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/rules_cros/+/3523710 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 :)