How to help minizip-ng find a locally built zlib-ng?

[AndrewAtAvenza]

I'm building zlib-ng as part of my build process but I can't see how to consistently specify that build as the one minizip-ng should use when building. I have a zlib on my system, but I do not want it to use that.

If I just build minizip-ng normally, it finds the system zlib and builds just fine. I've managed to force it -- in some circumstances -- to find it by specifying "-DCMAKE_FIND_ROOT_PATH=/path/to/my/zlib-ng/install/dir". That works from the command line, but when I try to add it to my main project's CMakeLists.txt using:

list(APPEND CMAKE_FIND_ROOT_PATH /path/to/my/zlib-ng/install/dir)

and then doing

find_package(minizip-ng REQUIRED HINTS /path/to/minizip-ng/install/dir)`

it doesn't work at all. Not becauese it can't find minizip-ng's config pacakge, but because it does but when it reads that it can't find zlib-ng. This seems to be at least partly because the minizip-ng config does find_dependency(ZLIBNG) which just wraps find_package(ZLIBNG) which ends up looking for:

ZLIBNGConfig.cmake
zlibng-config.cmake

neither of which is correct. It should be zlib-ng-config.cmake or zlib-ng.cmake. Since this is in the minizip-ng's CMakeLists.txt, I can't control this short of modifying that, which I'd rather not do.

I'm not sure what I can do to make minizip-ng use my build of zlib-ng without monkeying with the internals of minizip-ng's CMake. Anyone got a suggestion about what I should be doing here?

[AndrewAtAvenza]

I've found that I change the find_dependency(ZLIBNG) in minizip-ng-config.cmake to find_dependency(zlib-ng) the problem goes away. I'm wary of calling for that change though I'm honestly not sure how find_dependency(ZLIBNG) ever works. Unfortunately, this doesn't help much since that's in a generated file.

It's also not clear if that config file is being generated from boilerplate by CMake or if that's hand-written logic in the zlib-ng project.