[roll] Roll fuchsia [ffx] Making ffx_plugin deps explicit

The GN template ffx_plugin() adds 2 dependencies as part of the
implementation of the template. One of these ffx/core:lib is part
of the refactoring of the ffx framework.

This change removes the implicit adding of these dependencies and
makes it explicit in each BUILD.gn file for the subtools and plugins.

The advantage of this is that now changes can be made incrementally to
specific tools vs. having to change the template and related macros for
all tools at once.

This also cleans up some `use ffx_core as _;` statements where the
subtools no longer require the legacy ffx_plugin macros, which should
have a positive impact on the build graph.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1188195
Original-Revision: 77d141651a89d9ab60dea42e5438ead1827a47d4
GitOrigin-RevId: f444471a98fe456959504d96ff9c1f37930c1c01
Change-Id: Ib5429148a756594765e42822c795ec5bd918fb01
1 file changed
tree: c8ac3bc66e4a26f145a788245760b046b2caed1a
  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.