commit | 028b80a86001f312de7d9456a563e9e3a1050b58 | [log] [tgz] |
---|---|---|
author | David 'Digit' Turner <digit@fuchsia.infra.roller.google.com> | Mon Sep 16 20:14:28 2024 +0000 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Sep 16 13:16:18 2024 -0700 |
tree | 0fe09b5c4b04c91e6e74b698423b7b9595a6bc90 | |
parent | 62d1891c6e2b5ef7231c97815ab11ffa8a404809 [diff] |
[roll] Roll fuchsia [bazel_sdk] Override host tool paths when invoking ffx. This is a reland of [1], which should work thanks to [2]. Ensure that `ffx` and its plugins do not rely on the SDK manifest to locate the host tool they may invoke at runtime, by passing their location directly on the command line. New functions are added to `ffx_tool.bzl` to retrieve the start of the command-line invocation, that includes the necessary `--config "sdk.override.<tool1>=<path1>,sdk.override.<tool2>=<path2>"` argument. This is required to allow moving the generation of the IDK to the Bazel workspace. In this scenario, host tools will be built on-demand as Bazel targets, and their location cannot be predicted before the build, making it difficult to write them to the SDK manifest in advance. (The SDK manifest will instead contain Bazel labels such as `@fuchsia_idk//tools/x64:cmc` that `ffx` definitely cannot convert to a proper host path on its own). [1]: https://fuchsia-review.googlesource.com/c/fuchsia/+/1114415 [2]: https://fuchsia-review.googlesource.com/c/fuchsia/+/1119632 Original-Bug: 367274537 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1115539 Original-Revision: 957e159e5467bb29f5994ad1a109605cc8bda913 GitOrigin-RevId: faa99204b49ce09152e4c252576e4c182799a925 Change-Id: I6f5fb6ba79f964a6b0effc5bcbeb2422604df82b
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 via the IRC channel #fuchsia
on Freenode.
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
.