So, is there a way to build opencv_world with cmake? I need to use the xfeatures2d module to use SURF and also the world300.lib for my project. Since world300.lib and world300d.lib are available in the prebuilt libraries for opencv3.0.0 shipping from the opencv website and the xfeatures2d is in the opencv extra modules, is there a work-around to solve this issue?
Have you already tried to set the "BUILD_opencv_world" value in the CMake-GUI?
Do you have any error message?
Related
I have tried many methods to build a 32-bit version of OpenCV version 4.0.1, however to no avail. I have tried using CMake and the file I require is opencv_world401.dll
May I know if anyone has any steps for me to follow to build the 64 bit source code so that I can have a complete 32-bit package in return? It seems there will be missing files when I use CMake.
Thank you!
Tried using CMake to build the 64 bit source code into a 32 bit package
Currently OpenCV_world401.dll is giving me a winerror 193
I have the same problem. It would be resolved easily. Firt, you need to download your intended version, in this case, under OpenCV – 4.1.2 section choose Windows from https://opencv.org/releases/.
Then, download the executable file, run it, and extract it wherever you want. Afterward you will be able to find, for example, opencv_world401.dll under "opencv\build\x64\" folder.
The opencv source code is platform in-dependent, which means you can build dll/so files for different platform with this same source code tree. But to get a Win32 build you'll have to make some change during "Configuration" step, because by default it will generate a x64 platform build.
Basically that's the only change required.
If you can read Chinese, here's a detailed tutorial for you to reference:
https://www.csdn.net/tags/OtDaQg0sODk1MS1ibG9n.html
I am using Code::Blocks with wxwidgets and I have include and lib folders under Document\wxwidgets. I am very new to c++ libraries. In Code::Blocks project initialization, I entered the location for wxwidgets. Then in setting/global enviornment variables I entered in base the Document\wxwidgets again. Still, I am not able to run the app. It shows the error in the include/wx/platform.h file where it says
C:\Users\Programming coder\Documents\wxwidgets\include\wx\platform.h|148|fatal error: wx/setup.h: No such file or directory|
I am not able to solve this and would appreciate some help. Also I checked and the wx folder does not seem to be there in the location. I don't know if that is normal.
Also, I downloaded the headers(include) from the wxwidgets github repo download page, wxWidgets-3.1.1-headers.7z. Any help appreciated.
Also, I am aware some questions exist already, but their problems are in different because most are using linux. Also I am using Code::Blocks IDE.
You need to build wxWidgets itself before building the applications using it. Its build process will create the setup.h file which is currently missing.
Note that, in principle, you could also use precompiled binaries, but in this case you must use exactly the same compiler as was used for compiling them, i.e. TDM gcc.
I cannot directly download boost library nor quantlib from sourceforge.net/ due to web control inside company. So I downloaded QuantLib v1.8.1 from github, added linking to boost library v1.60 (I also tried v1.61) which is available in the share folder (I tested, boost library works fine), and tried to build under VS2015 x64-release.
The error message I got was (after processing to errors.cpp):
C2757 'boost': a symbol with this name already exists and therefore this name cannot be used as a namespace name.
I'm wondering if it's due to a setup error? How to fix it?
Thanks.
I am using opencv 3.0.0 libraries for an object tracking project for which I need the SURF class functions and interfaces.
I recently learnt that it is now in the opencv_contrib module that needs to be added to the opencv libraries. I have the following questions:
1) Is it possible to build only this module into my existing opencv libraries that I extracted using the opencv.exe downloaded directly form their website (I did not build it using CMake the first time)
2) Is it ok to rebuild the entire opencv3.0.0 library with the extra modules and to keep the pre-built libraries in seperate directories?
3) If (2) is not possible, is there a way to erase all the opencv 3.0.0 library files and start fresh with extra modules included?
I am very new to this and I am using OpenCV to complete an assignment on object tracking.
No,its not possible. Try getting a git version of OpenCV3.0 and OpenCV_contrib3.0 and use Cmake to build it from the source.
Why do you want to keep the old pre-compiled files in a separate directory?
You cannot use it anyways.
Yes, you can do that. You can save some disk space if you delete the older ones.
I am attempting to build Doxygen using VS2013. I have downloaded the project from GitHub and I have installed Flex and Bison. When I attempt to build, it fails due to reference to Xapian header files that it cannot find/open. Xapian was not listed as a prereq for this so I don't know if I need to install something else of if it is already a part of the Doxygen package and I need to correct something in VS2013 to resolve the issue. Thanks.
Note that Xapian is only needed for the external search engine (doxysearch targets).
Next to building Xapian from source you can also download prebuild xapian libraries for Windows from here: http://ftp.stack.nl/pub/users/dimitri/xapian_doxygen_win.zip
Doxygen supports a range of search options, one of which depends on Xapian, but unfortunately this dependency doesn't seem to be documented in the installation notes. There are instructions for building Xapian on Windows, which also include pre-built binaries, although as I'm not a Windows user I can't tell you exactly which archives you'll need to get things working. xapian.h is in the xapian-core source code (it's the main Xapian header file, used when compiling any code that uses Xapian for search features).
If you run into problems building or installing Xapian on Windows, I'd suggest posting to the xapian-discuss mailing list. (The person who was maintaining the Windows build system is stepping down, but hopefully someone will be able to help out.)