commit | bbd2d8c8890f3c21f268e9037b0e23dbc64d58e0 | [log] [tgz] |
---|---|---|
author | davidben <davidben@google.com> | Wed Nov 20 14:04:59 2024 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Nov 20 14:06:01 2024 -0800 |
tree | a5c86f5868a9d8f9a5bcc4e1e6074220c03b91f0 | |
parent | 3145fd00faeddc413daccae01a10720f9956d902 [diff] |
Simplify how quiche platform files are incorporated There's a circular dependency between, say, quiche_core and quiche_platform_default. They're separated to apply strip_include_prefix, but this makes newer Bazel flag the unmarked dependency. The export headers were special-cased to work around this, but now logging headers are also part of this. If we instead just use includes, they can be part of the same target (which they logically are) and the circular dependency issue is gone. This fixes another blocker to updating QUICHE to newer Bazel. PiperOrigin-RevId: 698514759
QUICHE stands for QUIC, Http, 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.
There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:
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:
To contribute to QUICHE, follow instructions at CONTRIBUTING.md.
QUICHE is only supported on little-endian platforms.