[roll] Roll fuchsia [sdk][cpp] Compile C++ source code that is part of the SDK with stricter settings

Our customers use a variety of settings to compile Fuchsia SDK C++:

- The C++ distributed as source in the SDK
- The C++ generated by code generators in the SDK

Whenever Fuchsia platform devs makes a change that works in fuchsia.git
but otherwise might trigger a warning somewhere, we break their code.

We add a `sdk_extra_warnings` config target that is picked up by the
above, and causes them to be compiled with more warnings turned on.

The list starts with just "non-virtual-dtor" and
"ctad-maybe-unsupported".

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/865697
Original-Revision: b71a818f8c3b748b3f7364bb806add92666f9c77
GitOrigin-RevId: 6ebd6f79fe25a51e7494255382776339b25171e5
Change-Id: I93ff0217a0efd02a620c01cc1833c85c23308b94
1 file changed
tree: 0a86fda3538d635c9abac46ababb5b40a058ccea
  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.