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
pango layout problem with 1.16 branch on MSVC+cmake builds #7217
Comments
What language is it using? Does it still happen in Please check in your preferences file first, because if you just override it with |
Removing preferences doesn't appear to make a difference. I checked that previously and I reconfirmed just now. From my previous debugging efforts, the call in question is Lines 564 to 567 in 47fa4fa
Eventually |
Call stack, running against 47fa4fa:
There's no error thrown here, this is just the point at which I find |
This updates to pango 1.50.14 (from 1.50.12) which resolves wesnoth#7217 (but introduces wesnoth#7543).
Closed with #7793. |
Confirming this issue was caused by vcpkg's build of Pango 1.50.12. |
Game and System Information
Description of the bug
Been having a run of bad luck with building/running 1.16 on Windows. I was still using manual VC project files with MSVC for 1.16 branch until very recently. In my set-up some dependencies I built myself (eg OpenSSL), others I downloaded pre-built (eg SDL), others still I just used via vcpkg. This might sound like a horrible mix-up but it was working for me till recently.
pango is one of the dependencies I used from vcpkg. But I got to a point where the built binaries just wouldn't reach the main menu screen. Eventually I found it was a pango layout issue, resulting in the log file message:
Giving up on it once I found the issue was in pango, I switched to full vcpkg build via cmake which resulted in missing images due to SDL being unable to load images for some reason (discussed in #wesnoth-dev). Eventually the vcpkg baseline was updated and I am now at the point where I was to begin with - ie pango layout failing with vcpkg builds.
Steps to reproduce the behavior
Expected behavior
Normal execution through to the main menu screen.
Additional context
master branch builds fine, as do all builds on Linux.
The text was updated successfully, but these errors were encountered: