There are various ways to install it – through package managers such as Homebrew or Macports, or through the tarball + cmake. I had to look through a whole bunch of different sites to figure out what to do. Whether this is a good idea is completely besides the point.I’m using OpenCV for my 4th year design project and setting it up was a huge pain. Multiple OpenCV versions installed system-wide, with the option to chooseīetween them from Python. Modules in that directory, so by default import cv2 will give you your old version:īut you can force Python to search there (and search their first) with:Įt voila. Python won’t find the cv3/cv2.so link unless you explicitly tell it to search for Python site-packages directory now contains both the old cv2.so alias and now opencv3/cv2.so too. My solution was to create a directory opencv3 and put the new alias to 3.x.x in there, so that the We also can’t just rename the new one without Python getting upset about _init_ methods and such. We obviously can’t have two aliases in the same directory both called cv2.so, but it turns out usr/local/lib/python2.7/site-packages alongside the existing one. This is really easy these days, you can brew it just like you did with opencvĪt this point, you should be able to find your new library at:Īnd you’ll probably be able to find a new cv2.so inside Python module from our Python’s site-packages. Installing the library into the Homebrew cellar, and setting up a symlink to the Now we’re going to try and stick OpenCV 3 right in there alongside it. The Homebrew Cellar via a symlink in your Python’s site-packages. Take a peek inside /usr/local/lib/python2.7/site-packages and you’ll find anĪlias/symlink to the very same file. so file is what you’ve been using every time you’ve written import cv2. I installedĢ.4.12 with Homebrew ( brew install opencv) so it’s found at:Īnd inside that directory you’ll find the Python module: Next up, confirm where your current OpenCV version is installed. The following command produces the following output: Cellars and SymlinksĬheck that you’re using a Homebrew Python install by confirming that Here I’ll refer to Python 2.7, although you could of course do this for other versions by addingįlags to the homebrew installation of OpenCV. It should work for homebrew users like myself. It’s not pretty, it’s not necessarily advisable, but it works. With version 2.4.12 so that I can choose which one to use from Python. Here’s how I solved the problem, installing OpenCV 3.1.0 side-by-side on my system Meanwhile he was feeling terrifically trendy Like a lot of people, I’ve got a system-wide install of 2.4.X, That my friend and I were actually working from different versions of OpenCV, and as a result the simpleĪpplication wrapper written in Python-OpenCV was crashing even though everything Caffe Recently I’ve been working on a project that’s written in Python/OpenCV/Caffe.Īfter spending a while installing Caffe on OS X, I was pretty disappointed to find out > (0, 'usr/local/lib/python2.7/site-packages/opencv3') If you want to import the 3.x.x version, add the following line at the top of your script to temporarily add the new site-packages subdirectory to the PYTHONPATH:.usr/local/lib/python2.7/site-packages/opencv3/cv2.so $ ln -s /usr/local/Cellar/opencv3/3.x.x/lib/python2.7/site-packages/cv2.so \ Create another subdirectory inside site-packages, for example, /opencv3 and put a symlink to the 3.x.x cv2.so file in there:.usr/local/lib/python2.7/site-packages/cv2.so Homebrew Python imports that module via a symlink at:.Both the above libraries contain a Python module cv2.so, stored at a path similar (but not necessarily identical) to:.
brew install opencv3 creates /usr/local/Cellar/opencv3/.
Homebrew installs libraries to /usr/local/Cellar/.
0 kommentar(er)
