[roll] Roll fuchsia [bazel] Add host argument to bazel_action()

Previously, `no_sdk = true` would implicitly run the Bazel action for
the host. Now, an explicit indication of building for host is required.
This will allow Bazel actions for Fuchsia that do not require the SDK in
the future. `no_sdk = true` is required when `host = true`.

As shown below, build the steps appear as if the target is being built
for Fuchsia, just as it did before with no_sdk.
    //build/bazel/examples/hello_host(//build/toolchain/fuchsia:arm64)

The GN bazel_action() target //build/bazel/examples/hello_no_sdk no
longer builds because the host platform is no longer implied.

Original-Bug: 338009514
Test: fx clean && fx build //build/bazel/examples/hello_host
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1257046
Original-Revision: 7f6f8e197c851a2735de4a21460fda8a24e559b8
GitOrigin-RevId: 262f9c0444a0bbaa4a04354946ec1226ae300005
Change-Id: I771a00766c1b15d054909933058338ab7b60f669
1 file changed
tree: 839d780219c92c53fae6c91eed589b8808f2e9b4
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

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.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.