Release-Instructions.md
The following steps should be taken by project maintainers when they create a new release.
Create a new release and tag for the release.
(Xcode SPM tools do not pick up vMajor.Minor.Revision used in older releases. After 2.4.2 please do not include the v in the tag name)
Update the podspec and test it
Push the pod to the trunk
Note: We are no longer releasing a Carthage release as of 2.2.3. Developers are encouraged to build one themselves.
The following steps should be taken by project maintainers when they update minizip files.
brew install cmakecmake . -DMZ_BZIP2=OFF -DMZ_LIBCOMP=OFF -DMZ_LZMA=OFF -DMZ_OPENSSL=OFF -DMZ_ZLIB=ON -DMZ_ZSTD=OFF./CMakeFiles/minizip.dir/DependInfo.cmake it will give you the following information:./CMakeFiles/minizip.dir/flags.make it will give you the following information:HAVE_ARC4RANDOM_BUF HAVE_ICONV HAVE_INTTYPES_H HAVE_PKCRYPT HAVE_STDINT_H HAVE_WZAES HAVE_ZLIB ZLIB_COMPAT
Ignoring the ones starting with an underscore, like: "_BSD_SOURCE" "_DARWIN_C_SOURCE" "_DEFAULT_SOURCE" "_POSIX_C_SOURCE=200809L"
Set those flags in SSZipArchive.podspec (for CocoaPods) and in ZipArchive.xcodeproj (for Carthage)
Replace the .h and .c files with the latest ones, except for compat/*.{c,h}, which are customized to expose some struct in SSZipCommon.h.
Note: we can also use cmake -G Xcode . -DMZ_BZIP2=OFF -DMZ_LIBCOMP=OFF -DMZ_LZMA=OFF -DMZ_OPENSSL=OFF -DMZ_ZLIB=ON -DMZ_ZSTD=OFF to get the list of files to include in an xcodeproj of its own.