Introduction:
The day is a sunday and I reluctantly was checking with one of my interns about the opencv project I have been helping them complete. She, rohini, told me, that she is finding a "dll error: module not found" type error in opencv video operation. Now, at this point I decided to solve this issue by creating a fresh venv and downloading the files, run them and resolve. And hence starts the issues.
Naive-enough:
The naive me, tried to download opencv saying pip3 install opencv. That sadly ends in a 404 error from pypi; as the project is actually under the name opencv-python. Now, I write pip3 install opencv-python; some downloads start; but it again stops with the statement, 'ModuleNotFoundError: No module named 'skbuild'. Big oof!
So figures out.. skbuild is not some module to download. It is getting caused because of pip3 versioning. The solution to this issue is found from the github issue here; which is upgrade your pip using
pip3 install --upgrade pip
and then install opencv using
pip3 install opencv-python
This time I successfully installed opencv-python-4.4.0.46. Now, let's try to recreate the dll error. Now the most important thread regarding this seems to be the following github issue on tensorflow. It seems that in windows, there is a compatibility issue between tensorflow, cuda and cudnn's different versions. The possible solution is to find out which one supports which and then resolve the conflicts by downgrading/upgrading either one of them.
Now, that above thread is applicable for tensorflow <1.11.0. For 1.13, 1.14; use this thread to read and understand the suggestion.The solution regarding this is again the same, as of to use specific supported versions of cuda (10.0) against tf 1.13 and 1.14; as well as to add cuda and cudnn to the environment path.
So this is the small story related to opencv installation hazards and cuda, cudnn compatibility. Let me know if these helped, otherwise, I may help you dig more into the issues and resolve such issues.
Comments
Post a Comment