-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aiscm 0.24.2 does not build with OpenCV 4.6.0 #30
Comments
Ok, I have removed the OpenCV bindings. I am not maintaining aiscm at the moment. The FFmpeg bindings also don't work with FFmpeg beyond 4.4.3. |
Should the configure.ac checks for opencv be removed as well then? at https://github.com/wedesoft/aiscm/blob/master/configure.ac#L83. it causes this at configure time:
|
Removing these lines in (add-after 'unpack 'do-not-check-for-opencv
(lambda _
(substitute* "configure.ac"
(("PKG_CHECK_MODULES\\(OPENCV.*") "")
(("AC_SUBST\\(OPENCV_CFLAGS)") "")
(("AC_SUBST\\(OPENCV_LIBS)") "")))) But it then fails at
|
Ok, I had some more OpenCV samples in there, sorry about that. I just released 0.25.2 with the OpenCV samples removed. |
Thanks, building 0.25.2 without opencv was successful :-). |
Hi I was trying to update OpenCV in guix to 4.6.0 from 4.5.4.
The Guix QA build checker shows aiscm would fail to build with OpenCV 4.6.0, with error
https://bordeaux.guix.gnu.org/build/6d64c5dc-818b-470d-b55c-be5b4cccf643
libtool: link: ( cd ".libs" && rm -f "libguile-aiscm-tensorflow.la" && ln -s "../libguile-aiscm-tensorflow.la" "libguile-aiscm-tensorflow.la" )
libtool: link: ( cd ".libs" && rm -f "libguile-aiscm-core.la" && ln -s "../libguile-aiscm-core.la" "libguile-aiscm-core.la" )
opencv.cpp:364:16: error: no member named 'drawAxis' in namespace 'cv::aruco'
cv::aruco::drawAxis(img, camera, distortion, rvec, tvec, scm_to_double(scm_len));
Looking at OpenCV sources from 4.5.4 and 4.6.0, it appears
cv::aruco::drawAxis()
was an API in opencv-contrib and was removed around OpenCV 4.6.0 or so. It is probably an API not guaranteed to be stable.
Probably a good idea not to reference such APIs.
The text was updated successfully, but these errors were encountered: