The MacPorts package manager installs the minizip-ng library without the trailing -ng, and similarly leaves the -ng off of the minizip-ng-related cmake modules. Configuring and building leaves things in a state where the includes are found, and the binaries all are compiled, but the linker invocation is inconsistent: the no-ng library name is used when specifying its position in the files to be linked, but earlier, in the linker directive to hide the symbols in the minizip-ng library, the -ng is present again, even though that's the wrong name.
There was already code to handle this in CMakeLists.txt if a particular variable (minizip_LIBRARY) was set, but Findminizip-ng.cmake was not setting it. Shortly I will submit a PR that sets it.
The MacPorts package manager installs the
minizip-nglibrary without the trailing-ng, and similarly leaves the-ngoff of theminizip-ng-relatedcmakemodules. Configuring and building leaves things in a state where the includes are found, and the binaries all are compiled, but the linker invocation is inconsistent: the no-nglibrary name is used when specifying its position in the files to be linked, but earlier, in the linker directive to hide the symbols in theminizip-nglibrary, the-ngis present again, even though that's the wrong name.There was already code to handle this in
CMakeLists.txtif a particular variable (minizip_LIBRARY) was set, butFindminizip-ng.cmakewas not setting it. Shortly I will submit a PR that sets it.