qwe

.github/actions/common-setup/action.yml

@@ -38,6 +38,7 @@ runs:
 
     - name: Set up Vistual Studio Command Prompt (Windows only)
       uses: ilammy/msvc-dev-cmd@v1
+      id: msvc-dev-cmd
       if: runner.os == 'Windows'
 
     - name: Prepare the build environment

.github/scripts/build_env/windows.sh

@@ -1,15 +1,44 @@
 #!/bin/bash
 set -euo pipefail
 
-choco install --no-progress \
+choco install -y --no-progress \
   ninja \
   llvm \
   vswhere \
-  msys2
+  msys2 \
+  pkgconfiglite
 
-choco install --no-progress --source python \
+choco install -y --no-progress --source python \
   meson
 
-export PATH="C:\tools\msys64\usr\bin;$PATH"
+# Using bash as the shell means a symlink tool /usr/bin/link gets in the
+# path before MS's LINK.EXE.  It's not clear what the best workaround for
+# this is, so just move it out of the way for now.  Other ideas here:
+#
+# https://github.com/ilammy/msvc-dev-cmd/issues/25
+#
+mv /usr/bin/link.exe /usr/bin/gnu-link.exe
 
-C:/tools/msys64/usr/bin/pacman -S mingw-w64-clang-x86_64-gtk4 --noconfirm
+GTK_PATH="C:/gtk"
+GNOME_PATH="C:/gnome"
+
+git clone https://gitlab.gnome.org/GNOME/gtk.git "$GTK_PATH" --depth 1
+
+cd "$GTK_PATH"
+
+meson setup builddir \
+  --prefix="$GNOME_PATH" \
+  -Dbackend_max_links=1 \
+  -Dbuild-demos=false \
+  -Dbuild-tests=false \
+  -Dmedia-gstreamer=disabled \
+  -Dbuild-examples=false \
+  -Dglib:tests=false \
+  -Dharfbuzz:tests=disabled \
+  -Dharfbuzz:docs=disabled \
+  -Dgraphene:tests=false \
+  -Dgdk-pixbuf:tests=false \
+  -Dcairo:tests=disabled
+meson install -C builddir
+
+echo "$GNOME_PATH/bin" >>"$GITHUB_PATH"