-
Notifications
You must be signed in to change notification settings - Fork 828
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
Build fails on OSX with latest FFMPEG release #503
Comments
UPDATE Spent a little longer looking at this and, the fix or The fix was committed to the Also, I set Debugging the
This means that, irrespective of what I set I have absolutely no idea whether the My naive view is that the build should not go looking for However, I patched
And gave that a go ...
.. but ...
And about another 20 errors - so obviously merely resolving the original problem (i.e. getting the build to find the appropriate header files, libraries etc) isn't going to work. FYI. I also changed the tag to As I mentioned in my original post on this issue, my current work around-is to rollback So what I am going to do is fork I believe that what would be useful for Obviously this will be useful for my particular situation, but I also think it will be useful for cases where there is a need/desire to have a custom So I will fork, change it, and put in a pull request - I completely understand if the @justadudewhohacks and the other maintainers reject it. As I mentioned at the beginning this was more of an FYI / PSA :) |
@goulash1971 Did workaround in the meantime until your patch lands:
|
@clarsen Thanks. Your workaround got things compiling. |
@clarsen Thanks. This was a major PITA for me. |
@clarsen Thanks,it really works |
Thanks to @goulash1971 ! 👍 |
I installed successfuly but i have this issue : when i launched a program with |
Hi there - this is more of an FYI / PSA than an issue :)
I have been experiencing a build error on OSX Mojave ...
Looking at a bunch of other issues that have been raised and mostly solved, it appears that this is in part due to the presences of
tesseract
on my machine (see issue #179). Prior to this change the the brew formula forffmpeg
...Homebrew/homebrew-core@3e99e5d#diff-8f4deb87ce96b9c5efe97be3288bb406
..
tesseract
was not automatically installed and therefore when the auto-build executed the tesseract library was not found etc.I've checked that the tesseract header files are installed correctly by brew, and these seem to be in the right place (/usr/local/include/tesseract), so I am guessing that there is a problem with the opencv build scripts.
I haven't got time to start debugging all of that so my work around is (horribly) to rollback the ffmpeg install for the time being.
UPDATE
Whilst the build goes through I have 'amused' myself by digging into the CMake files for OpenCV and I think that the problem I am getting is related to this change ...
opencv/opencv_contrib@fdb575d#diff-cad4fd9d74cc81b36a9dc481ed253200
.. it looks like the
Tesseract_INCLUDE_DIRS
should be set (see https://github.com/opencv/opencv_contrib/blob/3.4/modules/text/cmake/FindTesseract.cmake).Anyway, there is a 'switch' that can block the inclusion of the
tesseract
OCR (OPENCV_FIND_TESSERACT
) ... just not sure where it could be set ... any ideas @justadudewhohacksThe text was updated successfully, but these errors were encountered: