AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Personally, I am currently fine with only one DLLĮNABLE_AVX -> ON // This and the following entries enable the use of special processor instructions which should speed up performance. This is easier for deploying since only one file needs to be located alongside the executable, but also increases the size of the application directory due to the (unnecessary) code of unused modules. I changed only the following entries and left the rest on defaultīUILD_DOCS -> OFF // I don't need the documentation since I look it up online anyway (or look directly in the header files)īUILD_EXAMPLES -> ON // Examples are quite useful to get a first impression of an algorithmīUILD_opencv_world -> ON // This builds a unified DLL containing the machine code for all modules. In my case, I build with Visual Studio 2015 for the 圆4 architecture, therefore, selecting Visual StuWin64Īfter this step, you see all the options (which are all read) you can configure your own build process. the compiler toolset of the Visual Studio version). A window opens where you need to specify the target toolset (i.e. The folder sources/opencv-master contains the source code from the git repository (which is also the folder referenced by the PDB files) cmake_build contains all the files created and needed for building. The build folder is the installation directory where the created binaries will be stored. I would recommend to store also the latest commit ID and save it in an appropriate text file ( version.txt) for future referenceĬreate the following folder structure (I downloaded the sources as zip file)
0 Comments
Read More
Leave a Reply. |