ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
Hi!
I don’t have a clear answer, but I’ll share my experience so far with Opencv module.
I recommend you to work with the at least sources in order to keep opencv and opencv contrib synced, and because releases of opencv contrib are not that frequent. If you are planning to keep it automatically updated, you might want to use scripts. In a bash script (update.sh):
!/bin/bash cd opencv && git pull cd ../opencv_contrib && git pull
then with powershell:
$src = "I:/opencv-master/opencv" $srcextra = "I:/opencv-master/opencv/opencv_contrib" $build = "I:/opencv-master/build" $target = "Visual Studio 15 2017 Win64" bash update.sh cd $build
rm -Recurse -Force CMake* cmake -G $target -T v140,host=x64
-DOPENCV_ENABLE_NONFREE=1
-DOPENCV_EXTRA_MODULES_PATH="../opencv_contrib/modules" ` ../opencv | Tee-Object -Variable RESULT if("$RESULT" -eq 1) { "cmake didn't succeed, exiting." exit } msbuild.exe OpenCV.sln /verbosity:m /m cd ..
2 | No.2 Revision |
Hi!
I don’t have a clear answer, but I’ll share my experience so far with Opencv module.
I recommend you to work with the at least sources in order to keep opencv and opencv contrib synced, and because releases of opencv contrib are not that frequent. If you are planning to keep it automatically updated, you might want to use scripts. In a bash script (update.sh):
then with powershell:
$src = "I:/opencv-master/opencv"
3 | No.3 Revision |
Hi!
I don’t have a clear answer, but I’ll share my experience so far with Opencv module.
I recommend you to work with the at least sources in order to keep opencv and opencv contrib synced, and because releases of opencv contrib are not that frequent. If you are planning to keep it automatically updated, you might want to use scripts. In a bash script (update.sh):
#!/bin/bash
cd opencv && git pull cd ../opencv_contrib && git then with powershell:
$src = "I:/opencv-master/opencv"
$srcextra =
"I:/opencv-master/opencv/opencv_contrib"
$build = "I:/opencv-master/build"
$target = "Visual Studio 15 2017
Win64" bash update.sh cd $build
rm -Recurse -Force CMake* cmake -G
$target -T v140,host=x64 `
-DOPENCV_ENABLE_NONFREE=1 `
-DOPENCV_EXTRA_MODULES_PATH="../opencv_contrib/modules"
`
../opencv | Tee-Object -Variable RESULT if("$RESULT" -eq 1) {
"cmake didn't succeed, exiting."
exit } msbuild.exe OpenCV.sln /verbosity:m /m cd ..
4 | No.4 Revision |
Hi!
I don’t have a clear answer, but I’ll share my experience so far with Opencv module.
I recommend you to work with the at least sources in order to keep opencv and opencv contrib synced, and because releases of opencv contrib are not that frequent. If you are planning to keep it automatically updated, you might want to use scripts. In a bash script (update.sh):
#!/bin/bash cd opencv && git pull cd ../opencv_contrib && git pull
then with powershell:
$src = "I:/opencv-master/opencv"
$srcextra =
"I:/opencv-master/opencv/opencv_contrib"
$build = "I:/opencv-master/build"
$target = "Visual Studio 15 2017
Win64" bash update.sh cd $build
rm -Recurse -Force CMake* cmake -G
$target -T v140,host=x64 `
-DOPENCV_ENABLE_NONFREE=1 `
-DOPENCV_EXTRA_MODULES_PATH="../opencv_contrib/modules"
`
../opencv | Tee-Object -Variable RESULT if("$RESULT" -eq 1) {
"cmake didn't succeed, exiting."
exit } msbuild.exe OpenCV.sln /verbosity:m /m cd ..