[build] Export shlib-compatible builds of Zircon static libraries

The static libraries built in Zircon and then exported for use in
the legacy build can sometimes be linked into shared libraries
there.  Make sure to export the shlib-compatible versions of
those libraries, so those links are valid.  Within Zircon, the
correct shlib or non-shlib version of a static library is always
found as needed because of the toolchain setup.  But that gets
flattened to a single binary for each library in the legacy
export.  The shlib-compatible build is always fine (if not
optimal) to use in non-shlib contexts, but not vice versa.

Bug: BLD-537 #done
Change-Id: I3801703eb5f501001e093a6d72d7123fe828bd91
2 files changed
tree: aea7a4fa7214ba5730319550c3583dacd65e2614
  1. boards/
  2. build/
  3. buildtools/
  4. bundles/
  5. docs/
  6. examples/
  7. garnet/
  8. peridot/
  9. products/
  10. scripts/
  11. sdk/
  12. src/
  13. third_party/
  14. tools/
  15. zircon/
  16. .clang-format
  17. .clang-tidy
  18. .dir-locals.el
  19. .gitattributes
  20. .gitignore
  21. .gn
  22. AUTHORS
  23. BUILD.gn
  24. CODE_OF_CONDUCT.md
  25. CONTRIBUTING.md
  26. LICENSE
  27. OWNERS
  28. PATENTS
  29. README.md
  30. rustfmt.toml
README.md

Fuchsia

Pink + Purple == Fuchsia (a new operating system)

What is Fuchsia?

Fuchsia is a modular, capability-based operating system. Fuchsia runs on modern 64-bit Intel and ARM processors.

Fuchsia is an open source project with a code of conduct that we expect everyone who interacts with the project to respect.

How can I build and run Fuchsia?

See Getting Started.

Where can I learn more about Fuchsia?

See the documentation.