commit | a411a265ceb5c7bbbcaacef88e1fd027adb05b2b | [log] [tgz] |
---|---|---|
author | QUICHE team <quiche-dev@google.com> | Tue Feb 13 06:53:01 2024 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Feb 13 06:54:15 2024 -0800 |
tree | 99eb0773ba9e99cabf41bedbf87ece0412c94ae4 | |
parent | bb4f68479fd8fa4738339cdcc5782b04b985b72b [diff] |
Fix issues required to build additional Quiche tests for Chrome This fixes build issues and test failures that occur when attempting to build the following test files as part of Chrome builds: - common/btree_scheduler_test.cc - common/print_elements_test.cc - common/wire_serialization_test.cc - http2/test_tools/hpack_example_test.cc - quic/core/deterministic_connection_id_generator_test.cc - quic/core/tls_server_handshaker_test.cc - quic/core/quic_generic_session_test.cc - quic/tools/connect_tunnel_test.cc - quic/tools/connect_udp_tunnel_test.cc Note that I've only tested this on Linux, so more minor changes might be needed to get all the tests passing on all platforms. This CL doesn't introduce any meaningful changes in functionality. PiperOrigin-RevId: 606606193
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.