vcpkg/scripts/test_ports/vcpkg-ci-opencv/vcpkg.json
Alexander Neumann fbf65ac0aa
[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)
2024-04-23 15:21:24 -04:00

74 lines
1.4 KiB
JSON

{
"name": "vcpkg-ci-opencv",
"version-string": "1",
"port-version": 5,
"description": "Port to force features of certain ports within CI",
"homepage": "https://github.com/microsoft/vcpkg",
"dependencies": [
{
"name": "opencv",
"default-features": false,
"features": [
"ade",
"contrib",
"dnn",
"eigen",
"ffmpeg",
"jpeg",
"nonfree",
"png",
"quirc",
"tiff",
"webp"
]
},
{
"name": "opencv",
"default-features": false,
"features": [
"gtk",
"dc1394"
],
"platform": "linux"
},
{
"name": "opencv",
"default-features": false,
"features": [
"cuda",
"cudnn",
"gstreamer",
"ovis",
"tbb"
],
"platform": "windows & x64 & !static & !uwp"
},
{
"name": "opencv",
"default-features": false,
"features": [
"freetype",
"gdcm",
"ipp",
"jasper",
"lapack",
"openexr",
"opengl",
"openmp",
"qt",
"sfm",
"vtk"
],
"platform": "!uwp & !(windows & (arm | arm64))"
},
{
"name": "opencv",
"default-features": false,
"features": [
"python"
],
"platform": "!uwp & !(windows & static)"
}
]
}