Add a libz-ng-sys crate, using the same sources with minimal duplication #98
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
libz-ng-sys uses the zlib-ng native API, rather than the zlib-compat
API. It exports the same Rust API (modulo the slight differences in
types), without the
zng_
prefixes, to make it easy to write Rustsoftware that works with both.
Add a separate Cargo.toml and README for libz-ng-sys.
Move the
build_zlib_ng
function frombuild.rs
tobuild_zng.rs
, anduse that as the build script for libz-ng-sys.
Add a cargo-zng script that creates the libz-ng-sys crate in a temporary
directory and runs cargo on it, to make it easy to run tests with:
Test libz-ng-sys in CI.