Skip to content

Latest commit

 

History

History
51 lines (34 loc) · 1.8 KB

Release-Instructions.md

File metadata and controls

51 lines (34 loc) · 1.8 KB
Raw

New ZipArchive release

The following steps should be taken by project maintainers when they create a new release.

  1. Create a new release and tag for the release.

    • Tags should be in the form of vMajor.Minor.Revision

    • Release names should be more human readable: Version Major.Minor.Revision

  2. Update the podspec and test it

    • pod lib lint SSZipArchive.podspec

  3. Push the pod to the trunk

    • pod trunk push SSZipArchive.podspec

  4. Create a Carthage framework archive

    • echo 'github "ZipArchive/ZipArchive"' > Cartfile
    • carthage build --no-skip-current
    • carthage archive ZipArchive

  5. Attach archive to the release created in step 1.

Minizip update

The following steps should be taken by project maintainers when they update minizip files.

  1. Source is at https://github.com/nmoinvaz/minizip.
  2. Have cmake: brew install cmake
  3. Run cmake on minizip repo with our desired configuration: cmake . -DMZ_BZIP2=OFF -DMZ_LZMA=OFF
  4. Look at the file ./CMakeFiles/minizip.dir/DependInfo.cmake, it will give two pieces of information:
  • The list of C files that we need to include.
  • The list of compiler flags that we need to include: "HAVE_ARC4RANDOM_BUF" "HAVE_INTTYPES_H" "HAVE_PKCRYPT" "HAVE_STDINT_H" "HAVE_WZAES" "HAVE_ZLIB"

With the exception of the last two: "MZ_ZIP_SIGNING" "_POSIX_C_SOURCE=200112L"

  1. Set those flags in SSZipArchive.podspec (for CocoaPods) and in ZipArchive.xcodeproj (for Carthage)
  2. Replace the .h and .c files with the latest ones, except for mz_compat.h, which is customized to expose some struct in SSZipCommon.h and to provide support for optional aes.

Note: we can also use cmake -G Xcode . -DMZ_BZIP2=OFF -DMZ_LZMA=OFF to get the list of files to include in an xcodeproj of its own, from where we can remove unneeded zip.h and unzip.h.