Can anybody list some disadvantages/advantages to installing the Windows pre-built binaries? Also, what is the latest version (i.e. 2.4.5) of a pre-built binary able to be installed in a 64-bit Windows machine?
Will imperative features, specifically object tracking be uninstalled in the pre-built binaries?
Thanks.
One issue I found: The prebuilt binaries are built without TBB support e.g. SURF feature extraction is not parallelized. (And I suppose other functionality as well) This makes sense for applications that parallelize over images, but applications that depend on processing image by image (such as a live video stream) benefit from TBBs.
Also I don't really get (because it is nowhere mentioned I think) which parts of OpenCV are parallelized and with which method. When building the library you can chose one/some of plenty of parallel processing frameworks that OpenCV should use. However, it is not clear which parts are actually ready to work with every framework.
Partly wrong. It's compiled without TBB, but with Visual Studios PPL Concurrency framework, which also has support for parallel execution. But since not all the code has been ported to the new parallel interface, you can see speedups from switching to TBB in some cases.
Asked: 2013-06-19 15:18:23 -0600
Seen: 392 times
Last updated: Jun 19 '13
compared to what ? rebuilding (using cmake..) ?
imho, theres 3 situations, when you want to build your own libs ( instead of just taking the prebuilt ones )
in all other cases, the prebuild libs should behave the same
The prebuilt binaries are built without TBB support e.g. SURF feature extraction is not parallelized. This makes sense for applications that parallelize over images, but applications that depend on processing image by image (such as a live video stream) benefit from TBBs.
oh, that's right, another reason for building from source