Closed Xiliusha closed 1 year ago
Can you please explain in simple terms why you would want to build an install all four of these? (I think this is Windows-specific, and I don't know much about development on Windows.) Thank you.
Add "d" postfix to let Debug build type and Release build type exist together.
Add "zipstatic" target so I can using libzip on different projects. (Some required static link and others will link dynamically)
I think zlib is a good example:
😄Thanks!
This may not be Specific to Windows? I wonder what it looks like on Ubuntu.
Unix usually does not do debug/release builds, and static and dynamic libraries have different names: libzip.a and libzip.so, respectively.
Ok, I understand. On Windows, shared/static library both have a .lib file (this is the problem).😢
agree, Windows platform have some special static/dynamic library feature
Thanks for posting this, totally irrelevant but this helped me build a static library on macOS Big Sur.
Duplicating the complete libzip build definition is not an acceptable solution.
Also, this is not something we will do. If someone provides a low-impact patch, we will consider it.
Description I'm using CMake to compile libzip on Windows and found a problem. There is only a single compile target named "zip" and provide a option to determine shared/static. Most of the time it's fine. But when I try to install libzip on my computer, shared/static and Debug/Release type are all have the same name "zip". This question has been bothering me for a long time.
Solution Well, I have modified two CMakeLists.txt files. Now, all build types are there:
My custom CMakeLists.txt:
My custom lib/CMakeLists.txt: