[Prasadayus]

Follows the same approach as #1143 for 4.x.

Submodules are pinned at the 5.0.0 tag, so Windows ARM64 Build jobs are expected to fail for now. 5.0.0's vendored MLAS has no scalar fallback for its NEON kernels and fails to link without an ASM compiler. This is already fixed upstream in opencv/opencv#30331 and opencv/opencv#30332, not yet in any tagged release. Submodules will be bumped once available.

Opening as draft until then.

[asmorkalov]

Why is OpenCV disabled? OpenCV dynamically check OpenCL availability in runtime. The option looks redundant for me.

[Prasadayus]

@asmorkalov I have added this flag because current CI already builds arm64 with OpenCL off. Separately, the experimental win_arm64 binaries we built for 5.0.0 originally had it on, and testing on a Snapdragon X Elite (Adreno GPU) showed real test failures with it enabled

[asmorkalov]

Windows ARM build:

  INFO: calculating backend command to run: C:\Tools\Ninja\ninja.EXE
  [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

Encountered error while generating package metadata.

numpy

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
Traceback (most recent call last):
  File "C:\a\opencv-python\opencv-python\setup.py", line 10, in <module>
    from skbuild import cmaker, setup
ModuleNotFoundError: No module named 'skbuild'
Error: Process completed with exit code 1.