Just found that the project has been moved to GitHub with even newer releases.
Thanks for incorporating the patch into the development trunk. I tested it and it work fine. Great. Already a date for the new 0.7.4. release so we can tye our software to a released version?
QuaZIP moving to GitHub
Oh, and by the way, QuaZIP is being migrated to GitHub, so a PR would be even better than a patch, if you intend to send any.
I don't support CMake as I don't use it myself, so if you wish you can send me a patch to fix that CMAKE_BINARY_DIR and output naming issues (although I think the static suffix was meant to distinguish between the static version and the counterpart to DLL, used for dynamic linking). As for the main issue, looks like it attempts to do dynamic linking, just like if QUAZIP_STATIC wasn't defined. Surely it is in your project file, but just to double-check, could you post your compile output? I think...
Static MinGW build fails
Valid conclusion and for most of the obsolete functions, being required to keep them backward compatible, it is best to keep it in. So when I re-enable obsolete functions into my project, most issues get resolved and all will function until there will be a real breach in upcoming version of Qt. Which might take still a long time for Qt needs to be compatible as well. One issue though remains and that is for the use of the Q_FOREACH macro in JlCompress.cpp. I use a third-party library that has been...
Looking at this patch, I'm not sure whether it's worth the trade-off. All those checks really clutter the code and smell like macro abuse. As for using the bundled zlib, it's a really old idea, which may or may not be useful depending on the environment, so I'd rather leave it up to the user to provide all the necessary INCLUDEPATH and LIBS parameters on per-machine basis. And is it really that important to get rid of the deprecated functionality? I'd rather have it there than to have all those checks....
Sometimes a rebuild all does bring up some more issues to fix, sorry. Attached a new version of the patch with included now some changes do to the depricated use of Q_FOREACH. This has been depricated since Qt 5.7, so I added the pre-compiler check
Qt 5.10 support with Visual Studio 2017
Now that's good news! I'll look into it when I have time. The problem is, Minizip in QuaZIP includes some adjustments needed for it to work with non-file QIODevices, like QBuffer. I'll have to re-apply those adjustments to this Minizip fork or just borrow the appropriate parts of its logic. Both ways, it's not trivial.
Hi, I am also very interested in AES support. Read support alone would be great! I found this fork of MiniZip which brings support for AES and many other things, maybe this helps: https://github.com/nmoinvaz/minizip
support win32-msvc2015(Qt 5.9)
after a long time i spent for building ,building process was successfuly at end,it was deficault :) first download zlib then build zlib in VS2015 (zlibwapi.dll) after download quazip and run .pro file from quazip directory in .pro file i referenced zlib include and zlibwapi then added DEFINES+=ZLIB_WINAPI and then build was succesfuly the problem was in zlib version(zlib1211) but when i changed to older versions, it worked!
What do you mean by not working? It should work fine with almost any platform supported by Qt and zlib. Building it can be a pain, though.
support win32-msvc2015(Qt 5.9)
Hi, ok, thanks. I have a pending pull request for MXE at https://github.com/mxe/mxe/pull/1780 it's possible there will be some review also from there, and i'm also going to test this further, so let's keep it open, and i'll send here newer versions if any, or state that from my side it's ready.
I don't have any experience configuring pkg-config, so I'll just apply whatever you provide. Applied this patch in r288.
add pkg-config generation to qmake build
Applied in r287, thanks.
Replace Windows.h with windows.h
Replace Windows.h with windows.h
qmake-based install does not use QUAZIP_LIB_VERSION_SUFFIX
You can't change it, of course, but you can easily add another path with something...
How would one specify the path on the command line? I see that it's hard coded into...
Try r286. I fixed that path, but I have no access to Mac systems, so I have no idea...
Building debug version fails
Oh, sorry for my distraction, I didn't realize you had made a release.
Oh, sorry for my distraction, I didn't realized you had made a release.
Er? It's already there.
Thanks for the quick reaction. Looking forward to 0.7.3 :)
Applied in r282.
Fix CMake warnings
Here's the full patched CMakeLists.txt file, in case others want a convenient way...
Actually, I had to make additional fixes to the CMakeLists file, so I'll add a separate...
Fix CMake warnings
Static linking error - undefined reference
Done in r280. Edited a little bit, though.
Certainly! Here is my application (main) .pro entry: static { # everything below...
It's just a quick&dirty cut&paste as I was trying to get past this error. Anyway,...
Why CONFIG(staticlib)? If it's inside the “static” section anyway? Especially since...
Certainly! Here is my application (main) .pro entry: static { # everything below...
I think you need to define QUAZIP_STATIC in your project (that uses QuaZIP) to tell...
Static linking error - undefined reference
Hi, Sorry for the late reply. It's impossible with the current version of QuaZIP,...
Edit/Replace an existing file within an archive
Properly link quazip_static against its dependencies
Documentation bug about how to write zip files
You try to build statically, so you need to define QUAZIP_STATIC. It's in the RE...
Build Issue
Dear Sergey, indeed, i didn't take into account that one might use other zlib implementation,...
Static build related fixes
I've applied it in r268, but only the part that defined QUAZIP_STATIC. I didn't apply...
Static build related fixes
That was quick, thank you for accepting this patch!
Add lib_version_suffix to static lib
Add lib_version_suffix to static lib
Done.
tag for 0.7.1
Guess, it's r250.
tag for 0.7.1
On Qt5 #ifdef Q_WS_WIN is just false. You won't get any compile errors. You'd only...
Qt5 compatibility issue
Fixed in r260, although I wonder why I never got any errors on Qt5.