[roll] Roll fuchsia [bazel] add hlcpp visibility support to generated sdk

This CL adds a mechanism which lets us inject visibility into the hlcpp
bindings to restrict their usage. The mechanism at play here lets us
decide visibility on a per SDK basis which is important to make it so we
don't break our OOT users while still restricting the in-tree users.

The CL restricts usage to the fuchsia_sdk and internal_sdk since there
are libraries that are still using hlcpp but it prevents usage in other
locations in-tree.

Original-Bug: 406789405
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1238428
Original-Revision: 9a3a215ee90e1d305d35b455823489171d67885d
GitOrigin-RevId: 3e6fc56b12667d533b6b27905d96bee50b2a194d
Change-Id: Ie2709cd11cddc3999788c03171b19c294c20afe7
1 file changed
tree: 25468c1ae16b1cbf2fc06df3e35ccdd8f1b4ecaa
  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.