[roll] Roll fuchsia [fx][rust3p] Call ninja directly instead of `fx build`

This removes the warning from `fx build` that directs users to use GN
targets instead of Ninja outputs.

I opt to not use GN target for build in this particular case because
it doesn't improve the script. In fact it makes it slightly worse
because moving the GN target would requiring changing this script, which
building the Ninja output directly does not, and we'll need to hardcode
the path to the Ninja output anyways to invoke it.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1089714
Original-Revision: d65f2563711ab51cc715315bd4b4a35a345a13ae
GitOrigin-RevId: 27c6c0aedcefb6af8f1a05e34b3e028bf5f7ec95
Change-Id: I1b927f9f0003fca20dcaa48ad6199b69679d7881
1 file changed
tree: 14097552fd547ba0865ab2b4d1a3d8b9dfea7bf1
  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 via the IRC channel #fuchsia on Freenode.

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.