-
Notifications
You must be signed in to change notification settings - Fork 6.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tiff build failure #38116
Comments
You are stumbling over CMake 3.29.1. Downgrade, and reinstall all ports which were built with that version. |
All of tiff and not just the webp feature, then. Ugh. Thanks for the explanation @dg0yt ! I really do appreciate your work on the GDAL-related packages her 🙏 |
@dg0yt I'm finding it difficult to downgrade or tell vcpkg to use my downgraded version. The GitHub runners have 3.29.1 and installing cmake 3.28.4 via pip or the lukka/get-cmake action (which I've seen others do) doesn't work. In the tiff build logs I still only see references to 3.29.
|
You can try PR 38017 to see if it can solve your problem. |
@sgillies Does it compile normally after you downgrade cmake to 3.29.0 or upgrade to 3.29.2? |
@jimwang118 I'm using GitHub Actions, where the runners didn't have 3.29.2 until yesterday, and found it too difficult to convince vcpkg to not use the pre-installed cmake. So I went with an overlay port for vcpkg-cmake-config. |
@sgillies Is your issue solved now? |
@jimwang118 I don't know for certain. I haven't had the free time to see if my overlay port can be removed. GHA windows-latest runners have cmake 3.29.3 now, so I'll presume the problem is fixed and close this issue. Thanks for the support! |
Operating system
Windows
Compiler
No response
Steps to reproduce the behavior
The tiff port builds with zstd and lerc features, but not with webp. Specifying this in my project's vcpkg.json results in a non-finishing build.
Log excerpt is included below.
Failure logs
In
config-x64-windows-out.log
:Additional context
@dg0yt I'd try to sort this out myself but I have no Windows computer.
The text was updated successfully, but these errors were encountered: