| commit | a2e8126848c451d1edab811fc3ab6bff0858d65d | [log] [tgz] |
|---|---|---|
| author | George Burgess IV <gbiv@google.com> | Fri Feb 25 23:43:32 2022 -0800 |
| committer | George Burgess <gbiv@chromium.org> | Wed Mar 23 17:23:07 2022 +0000 |
| tree | c1ef66fcf688b0256dda807dd1574a5a3960a456 | |
| parent | 6453254e30abbf772ca2d8a8a4e337489229dc35 [diff] |
platform: parameterize toolchain defs
This is a series of nop changes that hopes to remove the duplication
between toolchain/platform definitions. The intent is to make each
platform definition much more compact than in prior CLs.
BUG=b:220355021
TEST=`bazel build --platforms="$x" ...` in drydock, for each $x in the
platforms we currently define.
Change-Id: I3dc11adfb6bc845800112afaa65fc212f31c9961
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/rules_cros/+/3503958
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 :)