[roll] Roll fuchsia [bazel_sdk] Fix manifest shard include paths

There is a problem where fuchsia_component_manifest() will not build the
correct include paths for a fuchsia_component_manifest_shard() target
declared in the main workspace. That is because the workspace root will
be an empty string in those cases.

Original-Bug: 380902086
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1172741
Original-Revision: a95d412785986a1ef1129c05e6fb0c6b376920c4
GitOrigin-RevId: 325ab1b3a6a9e4727d20ba646ab690c3bc338aff
Change-Id: I77e79171bdd278cd7d1d41cc8dff27ec29020e46
1 file changed
tree: 850a1e84d2648736feb466439033bd2e585d0215
  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.