[GH-ISSUE #243] ZLIB_ROOT ingored warning #194

Closed
opened 2026-05-05 11:53:32 -06:00 by gitea-mirror · 8 comments
Owner

Originally created by @John-Colvin on GitHub (Aug 30, 2019).
Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/243

Originally assigned to: @jmcnamara on GitHub.

CMake Warning (dev) at CMakeLists.txt:163 (find_package):
  Policy CMP0074 is not set: find_package uses <PackageName>_ROOT variables.
  Run "cmake --help-policy CMP0074" for policy details.  Use the cmake_policy
  command to set the policy and suppress this warning.

  CMake variable ZLIB_ROOT is set to:

    C:\Users\John Colvin\AppData\Local\dub\packages\xlsxd-3.1.8\xlsxd\\install_dir\zlib

  For compatibility, CMake is ignoring the variable.

I'm guessing you should set the policy in CmakeLists.txt, but I don't really know cmake

Originally created by @John-Colvin on GitHub (Aug 30, 2019). Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/243 Originally assigned to: @jmcnamara on GitHub. ``` CMake Warning (dev) at CMakeLists.txt:163 (find_package): Policy CMP0074 is not set: find_package uses <PackageName>_ROOT variables. Run "cmake --help-policy CMP0074" for policy details. Use the cmake_policy command to set the policy and suppress this warning. CMake variable ZLIB_ROOT is set to: C:\Users\John Colvin\AppData\Local\dub\packages\xlsxd-3.1.8\xlsxd\\install_dir\zlib For compatibility, CMake is ignoring the variable. ``` I'm guessing you should set the policy in `CmakeLists.txt`, but I don't really know cmake
gitea-mirror 2026-05-05 11:53:32 -06:00
  • closed this issue
  • added the
    bug
    cmake
    labels
Author
Owner

@jmcnamara commented on GitHub (Aug 30, 2019):

I think this may be a duplicate of #242 Can you check, and if it is, add your comments/analysis over there and I'll try to reply in one place.

<!-- gh-comment-id:526530108 --> @jmcnamara commented on GitHub (Aug 30, 2019): I think this may be a duplicate of #242 Can you check, and if it is, add your comments/analysis over there and I'll try to reply in one place.
Author
Owner

@John-Colvin commented on GitHub (Aug 30, 2019):

I don't think so, but it's possible if this was fixed it would fix #242

Someone with more knowledge about cmake would probably know better.

<!-- gh-comment-id:526589128 --> @John-Colvin commented on GitHub (Aug 30, 2019): I don't think so, but it's possible if this was fixed it would fix #242 Someone with more knowledge about cmake would probably know better.
Author
Owner

@evanmiller commented on GitHub (Aug 31, 2019):

@John-Colvin What version of CMake are you using?

<!-- gh-comment-id:526838718 --> @evanmiller commented on GitHub (Aug 31, 2019): @John-Colvin What version of CMake are you using?
Author
Owner

@Alexhuszagh commented on GitHub (Sep 3, 2019):

@evanmiller This is actually an issue with new CMake versions. Confirmed as of Cmake 3.14.5, the error makes it clear this has been an issue since CMake 3.12.

<!-- gh-comment-id:527500603 --> @Alexhuszagh commented on GitHub (Sep 3, 2019): @evanmiller This is actually an issue with new CMake versions. Confirmed as of Cmake `3.14.5`, the error makes it clear this has been an issue since CMake `3.12`.
Author
Owner

@Alexhuszagh commented on GitHub (Sep 3, 2019):

@John-Colvin Let me know if the following PR works for you:
https://github.com/jmcnamara/libxlsxwriter/pull/246

<!-- gh-comment-id:527510421 --> @Alexhuszagh commented on GitHub (Sep 3, 2019): @John-Colvin Let me know if the following PR works for you: https://github.com/jmcnamara/libxlsxwriter/pull/246
Author
Owner

@jmcnamara commented on GitHub (Sep 5, 2019):

@John-Colvin Can you test the proposed fix.

<!-- gh-comment-id:528253456 --> @jmcnamara commented on GitHub (Sep 5, 2019): @John-Colvin Can you test the proposed fix.
Author
Owner

@Alexhuszagh commented on GitHub (Sep 8, 2019):

@jmcnamara I'm very certain this should patch the issue, and at the very least, it will patch a similar issue due to CMake introducing a backward compatibility issue, so it might be preferable to commit any changes if there's no reply.

<!-- gh-comment-id:529210568 --> @Alexhuszagh commented on GitHub (Sep 8, 2019): @jmcnamara I'm very certain this should patch the issue, and at the very least, it will patch a similar issue due to CMake introducing a backward compatibility issue, so it might be preferable to commit any changes if there's no reply.
Author
Owner

@jmcnamara commented on GitHub (Sep 8, 2019):

@Alexhuszagh Agreed. Fix is merged.

@John-Colvin I'm closing this issue. You can test against the current master to see if your issues is fixed. If it isn't then open a new issue, with details on how to reproduce, or post a follow-up here.

<!-- gh-comment-id:529231069 --> @jmcnamara commented on GitHub (Sep 8, 2019): @Alexhuszagh Agreed. Fix is merged. @John-Colvin I'm closing this issue. You can test against the current master to see if your issues is fixed. If it isn't then open a new issue, with details on how to reproduce, or post a follow-up here.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/libxlsxwriter#194
No description provided.