Up libzip requirement to 1.x for Unicode support#1356
Conversation
We need the ZIP_FL_ENC_UTF_8 flag to support encoding i18n names for 4.0.
It actually is still called libzip-dev in that PPA:
Built packages
libzip-dev library for reading, creating, and modifying zip archives (development)
libzip4 library for reading, creating, and modifying zip archives (runtime)
zipcmp compare contents of zip archives
zipmerge merge zip archives
ziptool modify zip archives
|
It seems that in fact 0.11 is sufficient to address this issue - however the Travis Linux C.I. comes with 0.10 which isn't enough... |
|
I thought you said it is 1.x that has the |
|
I have successfully just built the 1.30 version of libzip with AppVeyor but I spotted an issue on line 14 of
and the build log on that CI system reports - WITHOUT IT BEING AN ERROR:
Any ideas whether this is an issue? |
It does - it is present in |
|
I'm in the process of making the installation of dependencies more error aware. This will become an error in the future. It's probably an issue at runtime, if there is no compatible dll found on the user's system, as the dll is probably not part of the binary distribution now. |
|
I note that in some circles the old or |
|
@vadi2 while you upgraded travis (linux specifically), but Windows is still at 0.11.x. I am not yet sure what is installed on macOS. |
|
Ah, with regard to: I see that in the I will tweak our and see whether the AppVeyor CI build still has the same error message... Um, got the PR wrong - I mean I will try this on # 1355... |
|
🎆 OK to get the Windows build correct, after changing the following in to: we need the line in to: Yee ha! |
|
@vadi2 can you add the changes @SlySven mentioned above to this PR? There are 2 main reasons for it:
|
|
All done |
Brief overview of PR changes/additions
Added a random PPA I found that has a newer libzip. I'm not certain if it has the development headers, however.
Motivation for adding to Mudlet
We need the ZIP_FL_ENC_UTF_8 flag to support encoding i18n names for 4.0.
Other info (issues closed, discussion etc)
Addresses issues @SlySven's been running into here and here.