I'm using OpenCV 3.1.0, Cmake 3.4.1 and Visual Studio 2013. I'm trying to build libraries and following all steps exactly the same as tutorials but at configuration step at CMake there is no option that i can set library output path (e.g LIBRARY_OUTPUT_PATH) so lib files cannot generated.
How can I solve this problem?
The answer is in the question: "Can't create lib files with CMake". You can never make libraries with cmake. CMale is a tool for creating Makefiles to tell make how to create the libraries.
Usually libraries are installed in ${CMAKE_INSTALL_PREFIX}/lib so if you call cmake e.g. with -D CMAKE_INSTALL_PREFIX=../inst the libs, includes and all you need are installed in a directory inst beside your build directory.
You can also use -D OPENCV_LIB_INSTALL_PATH=mylib which is appended to CMAKE_INSTALL_PREFIX and will install to ../inst/mylib instead of ../inst/lib. So you first select the overall location using CMAKE_INSTALL_PREFIX and then append the directory for the libraries with OPENCV_LIB_INSTALL_PATH.
As an example if we want to build in a subdirectory build of the source tree root and want to install in inst beside, the recipe is:
# Go to openCV source directory
cd opencv-3.0.0
# Create a build directory (can be anywhere with any name)
mkdir build
# Go to the build directory
cd build
# Create the makefiles (referencing the source directory .. )
cmake -D CMAKE_INSTALL_PREFIX=../inst -D CMAKE_BUILD_TYPE=RELEASE ..
# Run make to compile and link the sources
make
# Copy the libraries, binaries, includes to ${CMAKE_INSTALL_PREFIX}
make install
# Go to your install directory
cd ../inst
Compiling takes a lot of time and can be done parallel using several cores of your CPU by make -j8.
cmake is just making the makefile for make to compile. And make install will copy the libraries to the install location. I added a recipe to the answer.
Your linker is called with an unknown option or most common one with a wrong syntax. Usually cmake and later make knows how to pass such paths. I guess there is some thing happening with it, e.g. a not escaped backslash is ignored. Even if using Windows it is often better to use slash instead if backslash in paths. In the meantime even Microsoft has realized that it makes no sense to use backslash if the hole rest of the IT world has used slash long before DOS was made and until today.
Asked: 2016-01-14 07:32:41 -0600
Seen: 2,402 times
Last updated: Jan 15 '16
