From fbf65ac0aadce828277227aff08dd1e9212a7fbe Mon Sep 17 00:00:00 2001
From: Alexander Neumann <30894796+Neumann-A@users.noreply.github.com>
Date: Tue, 23 Apr 2024 21:21:24 +0200
Subject: [PATCH] [CI] Don't test stuff which does not work due to static
 python (#38303)

opencv even has
`message(WARNING "The python module is currently unsupported on Windows
when building static OpenCV libraries")`

In general static python builds don't support extensions on windows as
such a pyd build against a static python can never be used.
What would work -> static extensions linked into a final executable.

There is no proper way to deactivate extensions if python was statically
build on windows.

Two questions remain here:
Should python be build dynamically on windows for static triplets so
that we get a broader CI test? (maybe add a forbidden feature for only
windows&static which allows building the static python instead)
---
 scripts/test_ports/vcpkg-ci-opencv/vcpkg.json      | 2 +-
 scripts/test_ports/vcpkg-ci-openimageio/vcpkg.json | 5 ++++-
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/scripts/test_ports/vcpkg-ci-opencv/vcpkg.json b/scripts/test_ports/vcpkg-ci-opencv/vcpkg.json
index 83bbc51bc7..9eea154ce3 100644
--- a/scripts/test_ports/vcpkg-ci-opencv/vcpkg.json
+++ b/scripts/test_ports/vcpkg-ci-opencv/vcpkg.json
@@ -67,7 +67,7 @@
       "features": [
         "python"
       ],
-      "platform": "!uwp"
+      "platform": "!uwp & !(windows & static)"
     }
   ]
 }
diff --git a/scripts/test_ports/vcpkg-ci-openimageio/vcpkg.json b/scripts/test_ports/vcpkg-ci-openimageio/vcpkg.json
index 0d449b94a5..36a5e77888 100644
--- a/scripts/test_ports/vcpkg-ci-openimageio/vcpkg.json
+++ b/scripts/test_ports/vcpkg-ci-openimageio/vcpkg.json
@@ -13,7 +13,10 @@
         "libraw",
         "opencv",
         "openjpeg",
-        "pybind11",
+        {
+          "name": "pybind11",
+          "platform": "!(windows & static)"
+        }
         "tools",
         "webp"
       ]