[roll] Roll fuchsia [build][bazel] Make zx_library() generate packages for the internal SDK.

This CL ensures that a zx_library() target that is published to the
"internal" SDK category will compile properly. The issue, as explained
in the associated bug, is that by default sdk_source_set() sets the
`include_base` to `//` for the "internal" category. This allows things
like `//src/foo:bar` to be visible as `@sdk_internal//src/foo:bar`
in Bazel rules.

However, for zx_library() targets, the include base is always the
`include` directory relative to the BUILD.gn where the target is
defined (Zircon artifacts do not follow common Fuchsia conventions),
so a value of `include` should be provided for these.

Before this CL, the headers were misplaced in the resulting SDK
atom, making the sources unusable in Bazel build commands.

Original-Bug: 114820
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/760202
Original-Revision: 0dc45b9f37ee419b896457fc4c028a8baf13e9ba
GitOrigin-RevId: 6ff9a8644e5eca0e7d19b0ea93cccbaec6e2c61e
Change-Id: I47bfeae27b09675fefcfa1e31f9f72c67882556a
1 file changed
tree: 3df493dc4797aafaae03dd8dd4df2db87078ada1
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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 via the IRC channel #fuchsia on Freenode.

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.