[roll] Roll fuchsia [bazel] Make all //build/bazel sub-directories packages.
Some sub-directories of //build/bazel are Bazel packages, i.e.
have a BUILD.bazel file that defines the package's boundary.
This allows referencing files there with //build/bazel/subdir:file.
However, this was not the case for //build/bazel itself and many
of its sub-directories, meaning that labels like
//:build/bazel/subdir/file were needed instead.
To reduce confusion, make //build/bazel, and most of its sub-directories
a Bazel package. This requires adding empty BUILD.bazel files at the
right location, and adjusting a few label references.
+ Move build/bazel/local_repositories/boringssl.BUILD to
build/bazel/repository_rules/boringssl_BUILD.bazel.
The directory contained a single file, and was never used
as a repository override like other local_repositories/
subdir.
+ Fix a few repository rule implementations to use
`repo_ctx.path(Label("@//build/bazel/subdir:file"))` instead
of `workspace_dir + "/build/bazel/subdir/file"` in order to let
Bazel know that the corresponding file is a repository rule input.
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1259945
Original-Revision: 61fc16dc7710baf7d95e42a736b7098fd186042c
GitOrigin-RevId: 6beecd48de5f4400ca7bfecf6823c6fa53e9a261
Change-Id: I6403bb765b70c14405dd61aca93d7d57d5270abf
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.