[roll] Roll fuchsia [bazel] Do not propagate defines to the exec config

Add an experimental flag prevent defines from propagating to
the exec config where host tools used in the build are built.

There are no known issues, but it seems better to avoid any
unintentional propagation and potential performance impacts.

Original-Bug: 478893794
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1485317
Original-Revision: fda1f2cd566692ace0ae7b90bdffd8503e83895b
GitOrigin-RevId: 40f081a8bd4f3dc2a15d25e672ddb5002eefcb01
Change-Id: I9150562a7c4c952967ba65186bc87cf918a7ca4f
1 file changed
tree: 837faeb24d919770c4b8f4c24dd0eb30c0db413e
  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.