I just got my new Raspberry Pi 3 and want to check if it is fast enough to finally bring some computer vision to my autonomous quadrocopter.
After a fresh Raspbian installation I followed the tutorial to install OpenCV 3.0 on Debian Jessie. For all those who did not yet use virtual environments with python, the tutorial covers the basic usage. Really nice! Unfortunately, the tutorial did not work for me with the newest OpenCV 3.1: CMake refused to recognize Python3, so I specifically added parameters for this:
cmake -D CMAKE_BUILD_TYPE=RELEASE \ -D CMAKE_INSTALL_PREFIX=/usr/local \ -D INSTALL_C_EXAMPLES=OFF \ -D INSTALL_PYTHON_EXAMPLES=ON \ -D OPENCV_EXTRA_MODULES_PATH=/home/pi/opencv_contrib/modules \ -D BUILD_EXAMPLES=ON \ -D PYTHON3_LIBRARY=/usr/lib/arm-linux-gnueabihf/libpython3.4m.so \ -D PYTHON3_PACKAGES_PATH=/home/pi/.virtualenvs/cv/lib/python3.4/site-packages/ \ -D PYTHON3_INCLUDE_DIR=/home/pi/.virtualenvs/cv/include/python3.4m \ -D PYTHON3_EXECUTABLE=/home/pi/.virtualenvs/cv/bin/python3 \ -D BUILD_opencv_python3=ON \ ..
Now CMake did find Python3 and OpenCV was installed on my Raspberry Pi 3:)
I did not see the exact timing, but the
make -j4 call took at most 1h 22min. Really fast when I compare it to my early tryouts with the Raspberry Pi 1 and OpenCV!
After the compilation, I found out that the additional step in the tutorial to create a symbolic link in the virtualenv from
~/.virtualenvs/cv/lib/python3.4/site–packages/ to /usr/local/lib/python3.4/site–packages/cv2.so was not needed because the installation was already inside the virtualenv folder.Now that my installation is finished, stay tuned for some experiments with the new setup…