You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This requires a Windows user to actually write those instructions and submit a PR.
Sure, and there's a draft of such instructions using vcpkg in the OP
Note that vcpkg's GTK is not very useful and misses various files. It's not recommended to be used by the GTK project, see gtk.org.
Would love to learn more here. Is this an inherent limitation of vcpkg, or just something someone would need to PR a fix to them? It worked well for me, but I've only validated as far as the basic relm4 getting started docs (a couple buttons and a bit of text in a window). It's very possible I just haven't exercised it enough to run into that yet.
I don't think this needs to use vcpkg, but the documentation should call out some path for ARM users. Vcpkg is what seems to have worked for me, while the existing documented options did not.
Or, if we want to say making the install work for arm is an upstream problem (in gvsbuild?), the docs should at least clarify that they currently don't work for Windows ARM
The three options for installing GTK4 here did not work for me on ARM: https://gtk-rs.org/gtk4-rs/stable/latest/book/installation_windows.html. All three required some x86_64 specific components.
But, I was able to get up and running by installing GTK via
vcpkg
.D:\vcpkg
; remember this path to use in env vars belowvcpkg install --recurse --allow-unsupported gtk libxml2 librsvg pkgconf
--allow-unsupported
can be removed after [graphene] remove arm & windows exclusion microsoft/vcpkg#43335GTK_LIB_DIR
isD:\vcpkg\installed\arm64-windows\lib
PATH
includesD:\vcpkg\installed\arm64-windows\bin
PKG_CONFIG
isD:\vcpkg\installed\arm64-windows\tools\pkgconf\pkgconf.exe
PKG_CONFIG_PATH
isD:\vcpkg\installed\arm64-windows\lib\pkgconfig
I assume similar instructions work fine on x86_64 too.
The text was updated successfully, but these errors were encountered: