[roll] Roll fuchsia [bazel] Drop "_tool" from host tool target names

Previously, the `*_binary_host_tool()` macros created a "<name>_tool"
target that wrapped the actual tool target "<name>". This drops the
"_tool" suffix to make use more straightforward. The underlying binary
name is preserved by putting it in a "<name>.actual" subdirectory,
which avoids having two targets with the same label. The subdirectory
name complies with symbolic macro naming requirements.

The result is, for example, a `.../fidlc` symbolic link that points to
`.../fidlc.actual/fidlc`

NO_IFTTT=This change renames the Bazel fidl_api_summarize target and does not need to be made to the GN file.

Original-Bug: 426130024
Test: fx bazel build --config=fuchsia --copt="-ffuchsia-api-level=4293918720" //build/bazel/bazel_idk/tests:build_only_tests_for_combinations //build/bazel/bazel_idk/tests:build_only_tests
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1445710
Original-Revision: 7374844950fefbb4d554a44105245a544436f308
GitOrigin-RevId: 26ae9ef71ba5d61b9354ed78d47187e6b069bdde
Change-Id: I8f1ef8dbb4467cf877f2680c611ac7ee2f62f4b5
1 file changed
tree: 39efc9c0a324557e9d9a24416e15063cee7f7386
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
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.