Saikari
Saikari
> @luadebug I fixed the link error with protobuf by refactoring the protobuf package (PR #7756). Since sentencepiece only needs to link on protobuf lite, how to use only protobuf...
> current state: > > CMake Error at /home/kekopom/.xmake/cache/packages/2505/o/opencv/4.11.0/source/cmake/OpenCVGenPkgconfig.cmake:113 (cmake_minimum_required): Compatibility with CMake < 3.5 has been removed from CMake. > > Update the VERSION argument value. Or, use the...
> > > current state: > > > CMake Error at /home/kekopom/.xmake/cache/packages/2505/o/opencv/4.11.0/source/cmake/OpenCVGenPkgconfig.cmake:113 (cmake_minimum_required): Compatibility with CMake < 3.5 has been removed from CMake. > > > Update the VERSION argument...
> leads to a different error, I assume that it fixed the error for now I suppose it leads to ``` error: D:\xm\xmake-repo\packages\o\opencv\xmake.lua:311: ...amdir\core\sandbox\modules\import\core\tool\compiler.lua:84: @programdir\modules\core\tools\gcc.lua:1020: C:\Users\Admin\AppData\Local\Temp\.xmake\250507\_C595EFB0B9474EA38934169C8482FD35.cpp:2:10: fatal error: 'opencv2/opencv.hpp' file...
It looks like linkdir for windows `arm64` is `x64` for `local arch`. Need some workaround like new implementation would support old implementation as well.. C:/Users/runneradmin/AppData/Local/.xmake/packages/o/opencv/4.11.0/954bb460d4834f52b7ff0e8b3ff4d938/x64/vc17/staticlib/opencv_dpm4110.lib
> @luadebug do you know what's happening? `C:\Program Files (x86)\Windows Kits\10\include\10.0.26100.0\ucrt\wchar.h(254): error C2664: '__n64 __uint64x1_t_to_n64(uint64x1_t)': cannot convert argument 1 from 'uint16x4_t' to 'uint64x1_t'` > Only related topic I could find...
> So what do we do? can we disable windows arm support for now? It looks like this package has windows@arm64 introduced exactly for 4.10.0->4.11.0... exactly for 2022 worker... about...
> Since you added `-DAARCH64=ON` should it be now aarch64 instead of "ARM64"? (in case of arm only) Afaik -DARM in case of `arm` but not `arm64` for arm64 it...
Well now need to check if MSVC Windows-2025 worker is being skipped as well as MSVC Windows-2022 worker, since they have same issue... https://github.com/opencv/opencv/issues/27401 Expected windows-11-arm worker succeed.
> Is it ready now? Yes it is ready.