mirror of
https://github.com/jmcnamara/libxlsxwriter.git
synced 2026-05-15 14:15:54 -06:00
[GH-ISSUE #405] Broken logic in FindMINIZIP.cmake #321
Labels
No labels
awaiting user feedback
bug
cmake
cmake
docs
feature request
in progress
long term
medium term
medium term
pull-request
question
question
ready to close
short term
under investigation
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/libxlsxwriter#321
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @hosiet on GitHub (Aug 2, 2023).
Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/405
We look into what
FindMINIZIP.cmakedoes:f43e53e018/cmake/FindMINIZIP.cmake (L92-L95)When enabling
USE_SYSTEM_MINIZIPand system libminizip is found, these lines basically look through system's/usr/include/zlib.hand look for strings likeVersion [0-9]+\\.[0-9]+(\\.[0-9]+)?.However, the
zlib.hheader never had such lines:This condition actually applies to all recent zlib releases.
I believe the logic in
FindMINIZIP.cmakemust be broken somewhere. Can you take a look?@jmcnamara commented on GitHub (Aug 2, 2023):
Thanks. I'll take a look.
@jmcnamara commented on GitHub (Aug 3, 2023):
There was a "Version/version" typo in the regex that prevented
FindMINIZIP.cmakefrom reporting the library found even if it was. I fixed that and the compilation works on macOS and Ubuntu 22.04. I want to do a bit more digging to see why this didn't turn up in the past since that code has been there since 2017 (maybe cmake behaviour has changed?).Anyway, if you get a chance can you test main to see if it works on your OS.
@jmcnamara commented on GitHub (Aug 3, 2023):
I think I found the reason this didn't fail before. It was due to another change/fix in #398.
Anyway, the good news is that the CI is passing again so I'm going to close this.