OpenCV 2 or 1

[Chris Colbert]

There are many minor annoyances that we ran into in some functions
that make it near impossible to support both opencv versions
regardless of whether or not we link header files.

For example, cvIntegral in 2.0 calculates the titlted_sum for any
dtype, while 1.x does not.

Stefan and I realized during the sprint that this would cause us to be
IF_THEn_ELSE'ing all over the place, making the code ugly, just to
support a 5 year old version of the library. (there are more examples
than just this one)

We thought it would be better to make OpenCV 2.0 a dependency, and
lobby ubuntu to update the OpenCV packages.

Cheers,

Chris

2009/11/4 Stéfan van der Walt <stefan at sun.ac.za>:
>
> Hi Holger
>
> 2009/11/4 SirVer <sirver at gmx.de>:
>> The Problem is that the function cvCalibrateCamera2 now allocates an
>> distortion array of size 1x5 while before it allocated a distortion
>> array of 1x4. I guess that opencv2 uses 1x5 while opencv1 (the one i
>> currently use) uses 1x4.
>
> Should should make it a priority to figure out which version of OpenCV
> is available before releasing 0.3.  Do you have any ideas?   I was
> hoping they'd have a function such as version(), but I think I'm out
> of luck.
>
>> Another point: generated c files in the repository are constantly
>> comming up as changed or merge conflicts for me. What is the reason to
>> keep .c files in the repository; i think it is fair to assume that
>> python developers who have a c compiler installed will also have
>> cython installed to generate the .c files.
>
> This has been a constant source of annoyance, so I wonder whether we
> shouldn't just stop tracking the C files.  We could always still
> include C files in the source distribution.
>
> Regards
> Stéfan
>