[roll] Roll fuchsia [bazel] Define //build/bazel/platforms:{host,default} and use them.

- Add `target_cpu` to gn_build_args.txt to expose its value
  to Bazel.

- Add a new //build/bazel/platforms:default target, as an alias
  to the fuchsia_${target_cpu} target matching the current
  args.gn target_cpu value.

- Change the definition of //build/bazel/platforms:host as an
  alias to the real platform definition, to ensure proper remoting
  when using it.

- Use them in template.bazelrc and remove two expansion parameters
  from the template.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1216210
Original-Revision: c8b704914140a5a015ca68196925b2108bed003b
GitOrigin-RevId: 07e381a3b9ca16ebdb3b8e28ee3996494fe8c44e
Change-Id: I089b6f6ef4aa309d2b98fa5d8c9c272b27afc5d9
1 file changed
tree: 59fa635b4ef4e82f0e0b9d13694b389f019f7c09
  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.