[roll] Roll fuchsia [bazel_sdk] Add flag to disable all targets.

Add a flag --@fuchsia_sdk//fuchsia:fuchsia_targets_enabled=false|true
that disables (marks target incompatible) almost every target is
instantiated by @fuchsia_sdk or by which their rule definition is
defined by @fuchsia_sdk.

Also introduces a `fuchsia_cc_library` `cc_library` drop-in macro that
marks itself target_compatible_with Fuchsia while also being
configurable by the above flag and exposes the COMPATIBILITY constraints
to `defs.bzl`.

Fixes some non-toolchain-related `@fuchsia_clang` targets that were
missing target compatibility attrs.

All in all, this change essentially lets workflows and builders in
pigweed.git become fully correct w.r.t Fuchsia-related build targets by
allowing these targets to be marked incompatible (and thus skipped) when
not using `--config=fuchsia`.

Original-Bug: 374121817
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1140376
Original-Revision: 65b3c42e502b15c0f9cff0e1a0b6dde67f85e3d7
GitOrigin-RevId: ca58fc405d362ee587bf24887e8f7a2db1ddc78d
Change-Id: I338597c9926b196a5872daee739afa9452b5b821
1 file changed
tree: df40681a80cbe02224bef12b6b37583606f5682a
  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.