| commit | 6e106a52f8cf4baf43b0efb9348adaeee88db534 | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Mon Jul 26 14:23:32 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jul 26 14:25:12 2021 -0700 |
| tree | b9bc02f5460065848d7bdca7fa170ba875228c73 | |
| parent | ce06ef5d2c149369269981ad5a48849873da14ee [diff] |
Add QUICHE_EXPORT macros in third_party/http2/adapter. Also to FrameTypeToString() in third_party/spdy/core/spdy_protocol.h, which is required for test_utils.cc to link in Chromium. QUICHE_EXPORT_PRIVATE is used for definitions that are compiled in production code but used from test code as well (otherwise linking the net_unittest Chromium target fails). QUICHE_NO_EXPORT is used in compilation units that are part of the net_unittest build target, because these are not linked into any other target. This macro is defined empty both internally and in Chromium and is meant to supress the presubmit error. Also clean up dependencies using build_cleaner. PiperOrigin-RevId: 386958565
QUICHE stands for QUIC, Http/2, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.
The canonical open-source QUICHE repository is at https://quiche.googlesource.com/quiche.
To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:
QUICHE is only supported on little-endian platforms.