| commit | 778a943f91931acb2014f8f831820148f81a4594 | [log] [tgz] |
|---|---|---|
| author | David 'Digit' Turner <digit@fuchsia.infra.roller.google.com> | Tue Nov 05 09:11:34 2024 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Nov 05 01:12:35 2024 -0800 |
| tree | f409cc076fd46187a8a01c5097f8695c839f6665 | |
| parent | b574a75260b370c4bb98eb348876883278b61486 [diff] |
[roll] Roll fuchsia [bazel_sdk] Support IDK repository as fuchsia_sdk_repository() input. Change the `generate_sdk_build_rules.bzl` to support IDK metadata files that contain Bazel target labels, instead of file paths. E.g. `@fuchsia_in_tree_idk//tools/x64:cmc` instead of `tools/x64/cmc`. Modify fuchsia_sdk_repository() to support a `local_paths` value that is an external repository label (e.g. `@fuchsia_in_tree_idk`) instead of a file path. Modify the fuchsia_sdk_repository() invocation for @fuchsia_sdk to actually use the @fuchsia_in_tree_idk repository that was introduced in previous CLs. Finally, add a new fuchsia_idk_repository() named @fuchsia_internal_only_idk and use it to populate @internal_sdk. Note that: - The content of @fuchsia_sdk is no longer directly usable in external Bazel workspaces, since it contains Bazel labels pointing to @fuchsia_in_tree_idk now. However, using the symlink generated by `fx build generate_fuchsia_sdk_repository` still works, since it now points to the final in-tree SDK. - Calling `fx build bazel_sdk_tests` still validates the content of @fuchsia_sdk with the Bazel SDK test suite (as it passes a repository override to point to the content of @fuchsia_in_tree_idk as well). + Update build/bazel/bazel_sdk/README.md accordingly to reflect the new state of things. Original-Bug: 367274537 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1110275 Original-Revision: 6274d5c73b01b112f0602a50da4bd7f4cfec93a0 GitOrigin-RevId: 923f0991cc37596dc792529d90b2b5c49ec033b7 Change-Id: I26728f4e778e2b9e23e3a521b175bfea55c689b4
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.