This project builds and defines the build2 package for miniz. Miniz is a lossless, high performance data compression library in a single source file that implements the zlib (RFC 1950) and Deflate (RFC 1951) compressed data format specification standards.
Make sure to add the stable section of the cppget.org
repository to your project's repositories.manifest
to be able to fetch this package.
:
role: prerequisite
location: https://pkg.cppget.org/1/stable
# trust: ...
If the stable section of cppget.org
is not an option then add this Git repository itself instead as a prerequisite.
:
role: prerequisite
location: https://github.com/build2-packaging/miniz.git
Add the respective dependency in your project's manifest
file to make the package available for import.
depends: libminiz ^ 3.0.2
The library can be imported by the following declaration in a buildfile
.
import miniz = libminiz%lib{miniz}
There are no configuration options vailable.
generate_export_header
function that is provided by CMake. So, there could be differences in symbol visibility.oss-fuzz
.miniz_tester
was considered. But as the original build system does not provide tests for this executable and compiling it fails on Windows- and MacOS-based configurations, it was removed.v3.0.2
points to a version with a valid implementation and configuration variables. Please see Issue #1 for more information.Thanks in advance for your help and contribution to keep this package up-to-date. For now, please, file an issue on GitHub for everything that is not described below.
Please, file an issue on GitHub with the new recommended version.
git submodule init
and git submodule update
to get the current upstream directory.upstream
directory, checkout the new library version X.Y.Z
by calling git checkout vX.Y.Z
that you want to be packaged.buildfiles
, and symbolic links accordingly to create a working build2 package. Make sure not to directly depend on the upstream directory inside the build system but use symbolic links instead.manifest
file if it has changed or add package update by using +n
for the n
-th update.master
branch.bdep ci
and test for errors.bdep ci
link to your CI tests.upstream
directory, checkout the new library version X.Y.Z
by calling git checkout vX.Y.Z
that you want to be packaged.buildfiles
, and symbolic links accordingly to create a working build2 package. Make sure not to directly depend on the upstream directory inside the build system but use symbolic links instead.manifest
file if it has changed or add package update by using +n
for the n
-th update.master
branch.bdep ci
and test for errors and warnings.bdep release --tag --push
to push new tag version to repository.bdep publish
to publish the package to cppget.org.