| commit | 3a31cdeb161ec22c8763d12959d993d5fdc0d3ad | [log] [tgz] |
|---|---|---|
| author | Matthew Maurer <mmaurer@google.com> | Thu Mar 09 15:13:55 2023 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Mar 09 15:13:55 2023 +0000 |
| tree | a952149182faf24c5a8bf376e988b94df981f63c | |
| parent | 54c69eaa6ba650755e05c7b9f544813f2fde9ecb [diff] | |
| parent | e50fd6c18584a2cf923623cf65a2753f5a2dbb0a [diff] |
Make libz-sys available to product and vendor am: e50fd6c185 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/libz-sys/+/2476419 Change-Id: I25a8c54abb7d6ad45a979415a8b83f881a451080 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
A common library for linking libz to rust programs (also known as zlib).
This also serves as the source for the libz-ng-sys crate, which builds zlib-ng natively (not in zlib-compat mode). See README-zng.md for details.
This crate provides bindings to the raw low-level C API. For a higher-level safe API to work with DEFLATE, zlib, or gzip streams, see flate2. flate2 also supports alternative implementations, including slower but pure Rust implementations.
This crate supports building either the high-performance zlib-ng (in zlib-compat mode), or the widely available stock zlib.
By default, libz-sys uses stock zlib, primarily because doing so allows the use of a shared system zlib library if available.
Any application or library designed for zlib should work with zlib-ng in zlib-compat mode, as long as it doesn‘t make assumptions about the exact size or output of the deflated data (e.g. “compressing this data produces exactly this many bytes”), and as long as you don’t also dynamically pull in a copy of stock zlib (which will produce conflicting symbols). Nonetheless, for maximum compatibility, every library crate in a build must opt into allowing zlib-ng; if any library crate in your dependency graph wants stock zlib, libz-sys will use stock zlib.
Library crates depending on libz-sys should use:
libz-sys = { version = "1.1.0", default-features = false, features = ["libc"] }
(Omit the libc feature if you don't require the corresponding functions.)
This allows higher-level crates depending on your library to opt into zlib-ng if desired.
Building zlib-ng requires cmake.
This project is licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in libz-sys by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.