We're relying on the DNN module of OpenCV which, prior to the latest release of the debian/kinetic/opencv3 used to work. The version that is currently being shipped is 3.3.1-dev which was the pre-cursor to 3.4.0 and is not a released version.
The previous version of the release of debian/kinetic/opencv3 used to work - this relied on a released version of OpenCV3 which was 3.3.1 (rather than 3.3.1-dev)
3.3.1 was released in October and 3.3.1-dev was in December so I can only imagine that the re-base for kinetic/opencv3 was done after December.
I installed a local version of OpenCV3.3.1 and syslinked the compiled cv2.so to where the ros packages are and the DNN module now works perfectly.
I understand that OpenCV3.4 is being discussed as an REP; In the meantime, would it be possible to revert back to 3.3.1 release rather than 3.3.1-dev?
Newbie here. I am having a similar problem with 3.3.1-dev. The code worked fine with a local 3.4. May I ask how did you syslinked the compiled cv2.so to ros?
Hello,
We're relying on the DNN module of OpenCV which, prior to the latest release of the debian/kinetic/opencv3 used to work. The version that is currently being shipped is 3.3.1-dev which was the pre-cursor to 3.4.0 and is not a released version.
The previous version of the release of debian/kinetic/opencv3 used to work - this relied on a released version of OpenCV3 which was 3.3.1 (rather than 3.3.1-dev)
3.3.1 was released in October and 3.3.1-dev was in December so I can only imagine that the re-base for kinetic/opencv3 was done after December.
I installed a local version of OpenCV3.3.1 and syslinked the compiled cv2.so to where the ros packages are and the DNN module now works perfectly.
I understand that OpenCV3.4 is being discussed as an REP; In the meantime, would it be possible to revert back to 3.3.1 release rather than 3.3.1-dev?