Use minizip-ng as .dll

[Naldesacker]

Hi all,

I'm linking minizip dynamically as a third-party component into my C++ project (using LoadLibraryExW() ). I'm using VS2017 with Toolset 14.11.

I started with minizip-ng version 3.0.0 which I checked out via git, used cmake 3.15.7 to create a solution and then used again VS 14.11 to build. I excluded BZip2 from solution. The VS-build succeeded, lib-files were created. I switched all included projects (liblzma, libzstd_static, minizip and zlibstatic) to dll (project properties ->General -> Target Extension and Configuration Type), this build succeeded as well. When loading the resulting minizip.dll in my project with the dependencies located in same folder, minizip lib is loaded and used. Obvsly, the dlls were also added to my projects project files.

As there is an error message popping up with this 3.0.0 version when packing a large file (~7GB), I wanted to repeat above process for minizip version 4.0.4. Here I find that compiling as libs works fine, but when building as dlls, the linker throws multiple errors like:
Error LNK2019 unresolved external symbol BCryptOpenAlgorithmProvider referenced in function mz_crypt_aes_set_key minizip D:\Projects\minizip-ng\Builds\mz_crypt_winvista.obj
These are references into bcrypt which is provided by Microsoft (Windows Kit). I already tried CMAKE flag CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS which did not change anything.

So my questions are:

1. Is minizip-ng foreseen to be deployable via dll?
2. Did I miss some documentation where it is described how to do it?
3. Does anybody know how to do it?
4. Is the exact Windows Kit version relevant? I used Windows SDK version 10.0.20348.0 today, according to cmake file the target is Windows 10.0.19045.

Thanks in advance!

[Naldesacker]

hmmm, not the smartest question after all. Found the BUILD_SHARED_LIBS flag in the cmake file to enable creation of dlls.