[roll] Roll fuchsia [build] Fix loadable_module() variants to copy into base root_out_dir

For the output file of a loadable_module() to be the input to
another target such as host_test_data(), there must be a copy
to the known location in the base toolchain's output directory
as is done for executables.  This doesn't come up for the
toolchains that target Fuchsia, since those generally only
consume the output files via metadata anyway.  But it does arise
with the linux_$cpu toolchains that support loadable_module()
targets that need to be used in other ways.

Original-Bug: 130483
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/899721
Original-Revision: 82728282d18a281818edd3f37c24aad534735096
GitOrigin-RevId: 073198d3a3182db0e973cf02831b4bc04597b421
Change-Id: I8a7461526918822988737d64bc179b1e361b2a4d
1 file changed
tree: 6566242edfd0416e0d3bebab2a8f306c5e8ea138
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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.