Building with --OpNav enabled? #184
-
Howdy BSK Team, have you been testing out the
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
Update, I think this is actually a case sensitivity issue. I did the following to resolve it:
On MacOS and Windows, I think this may not be an issue - calls to the OS file manager on those platforms will treat |
Beta Was this translation helpful? Give feedback.
-
@scout-andrew , Thanks for sharing this insight. As Pat says, we currently can't build on CI with opNav turned on, work in progress. If I create a branch with this fix, would you be able to pull and test it for us? Or, if you can make a branch with a PR on this fix, I'm glad to pull and test/review. |
Beta Was this translation helpful? Give feedback.
-
@patkenneally and @schaubh, thanks for the discussions! I've opened Issue #185 and PR #189 to resolve this issue - should be a quick and easy fix. |
Beta Was this translation helpful? Give feedback.
Update, I think this is actually a case sensitivity issue. I did the following to resolve it:
opencv
directory inside~/.conan/data
to force conan to re-download OpenCV.python conanfile.py --opNav True
, noted that OpenCV was re-downloaded+compiled, which included a file named OpenCVConfig.cmake. The build still failed, however, until...opencvConfig.cmake
is extremely close toOpenCVConfig.cmake
. Changingsrc/cmake/usingOpenCV.cmake
to look forOpenCV
instead ofopencv
, including changingopencv_FOUND
toOpenCV_FOUND
builds just fine.On MacOS and Windows, I think this may not be an issue - calls to the OS file manager on those platforms will treat
opencvCo…