[roll] Roll fuchsia [sdk][zircon-assert] Declare <zircon/assert.h> as implicit Ninja inputs.

Declare that //sdk/lib/zircon-assert target provides <zircon/assert.h>.
This is a very special case because:

- The header itself appears several times in the build tree, i.e.:

  - sdk/lib/zircon-assert/zircon/assert.h: the reference header.
  - zircon/system/public/zircon/assert.h: a symlink to the former.

- The //sdk/lib/zircon-assert:zircon-assert target itself has
  different definitions based on the GN toolchain it is evaluated in.

  Due to this, it cannot simply be declared in the 'public'
  argument of //sdk/lib/zircon-assert:headers without triggering
  GN header inclusion checks.

Without this CL, running the following command:

```
python3 build/ninja_implicit_inputs/check_tool.py \
  --build //zircon/public/sysroot_sdk
```

Generates a report complaining about any targets including zircon/assert.h
without a proper dependency. Such as:

```
//zircon/system/ulib/fbl:fbl(//build/toolchain:host_x64)
    zircon/system/public/zircon/assert.h

//tools/fidl/fidlc:lib(//build/toolchain:host_x64)
    zircon/system/public/zircon/assert.h

//src/lib/zbitl:zbitl(//build/toolchain:host_x64)
    zircon/system/public/zircon/assert.h

//src/lib/zbitl:internal.decompress-zstd(//build/toolchain:host_x64)
    zircon/system/public/zircon/assert.h

//tools/fidl/fidlc:fidl-lint(//build/toolchain:host_x64)
    zircon/system/public/zircon/assert.h

//tools/fidl/fidlc:fidlc(//build/toolchain:host_x64)
    zircon/system/public/zircon/assert.h

//sdk/lib/zircon-assert:zircon-assert(//build/toolchain:host_x64)
    sdk/lib/zircon-assert/zircon/assert.h

//src/lib/fxl:memory(//build/toolchain:host_x64)
    sdk/lib/zircon-assert/zircon/assert.h
```

The issue is that the path written in the depfile can be either
sdk/lib/.../assert.h or zircon/system/.../assert.h depending
on the include search directories that appear in the compiler
command, even if both paths point to the same content. Some
targets do depend both on //sdk/lib/zircon-assert and
//zircon/system/public through different dependency paths
and it's impossible to sort these at the GN or Ninja level.

By simply declaring that both paths belong to the same GN
label, the problem is removed entirely.

NO_IFTTT=No need to change the corresponding BUILD.bazel file

Original-Original-Bug: 462397407
Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1433591
Original-Original-Revision: e8e0bb832ddd477e569d8805765f508593d2a034
GitOrigin-RevId: 69fe651f91b2c6c8f54d90021ec520eebf39330b
Change-Id: I0d4f359b77c546b159a5d9bcfb19a7c0f018978f
Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1641056
Cr-Commit-Position: refs/heads/main@{#194237}
1 file changed
tree: 41718faafd14afdd1da461c39247284e94711d55
  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.