Revision history [back]

I have compiled the OpenCV library & places the dylibs into a folder and included the dylibs by writing LIBS += /myproject/...executablepath/opencv_lib/*.dylib in my projects .pro file

The above works if I have files in /usr/local/lib, however it does NOT work when these dylibs are not there in /usr/local/lib.

I want to create a QT app which "bundles" OpenCV with it, such that the user does NOT need to install OpenCV himself before running the app. Now that I have already included the dylibs in my project, why should the libraries need to be there in /usr/local/lib also?

Please help!

I have compiled the OpenCV library & places the dylibs into a folder and included the dylibs by writing LIBS += /myproject/...executablepath/opencv_lib/*.dylib in my projects project's .pro file

The above works if I have files in /usr/local/lib, however it does NOT work when these dylibs are not there in /usr/local/lib.

I want to create a QT Qt app which "bundles" OpenCV with it, such that the user does NOT need to install OpenCV himself before running the app. Now that I have already included the dylibs in my project, why should the libraries need to be there in /usr/local/lib also?

Please help!

I have compiled the OpenCV library & places the dylibs into a folder and included the dylibs by writing LIBS += /myproject/...executablepath/opencv_lib/*.dylib in my project's .pro file

The above works if I have files in /usr/local/lib, however it does NOT work when these dylibs are not there in /usr/local/lib.

I want to create a Qt app which "bundles" OpenCV with it, such that the user does NOT need to install OpenCV himself before running the app. Now that I have already included the dylibs in my project, why should the libraries need to be there in /usr/local/lib also?

Please help!