Skip to content

Building with --OpNav enabled? #184

Answered by scout-andrew
scout-andrew asked this question in Q&A
Discussion options

You must be logged in to vote

Update, I think this is actually a case sensitivity issue. I did the following to resolve it:

  1. Deleted the opencv directory inside ~/.conan/data to force conan to re-download OpenCV.
  2. Ran 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...
  3. I noted that opencvConfig.cmake is extremely close to OpenCVConfig.cmake. Changing src/cmake/usingOpenCV.cmake to look for OpenCV instead of opencv, including changing opencv_FOUND to OpenCV_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…

Replies: 3 comments 1 reply

Comment options

You must be logged in to vote
1 reply
@patkenneally
Comment options

Answer selected by scout-andrew
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants