Error:
/.../MITK-Superbuild-Release-nightly/CMakeExternals/Source/OpenCV/modules/highgui/src/loadsave.cpp:298: error: 'InputArray' has not been declared
on mbiMac03
Error:
/.../MITK-Superbuild-Release-nightly/CMakeExternals/Source/OpenCV/modules/highgui/src/loadsave.cpp:298: error: 'InputArray' has not been declared
on mbiMac03
there still is a problem with openCV and MacOS:
/.../MITK-Superbuild-Debug-nightly/OpenCV-src/modules/flann/include/opencv2/flann/lsh_index.h:89:81: error: no matching constructor for initialization of 'cvflann::LshIndexParams'
summary:
http://cdash.mitk.org/viewBuildError.php?buildid=146844
Assigned to Mr. Fetzer because the client is not claimed...
I think the problem is that OpenCV is built with the Clang compiler although the GCC compiler is selected for super build. Maybe OpenCV 2.3 is not Clang compatible. Nevertheless the right compiler should be passed to the OpenCV build We should look after this on a wednesday.
However building OpenCV 2.4 on my Mac separately using the Clang compiler work.
Taking a look at mbimac08, I found out that the build started to fail on 5th of June, before that no openCV related errors occurred.
The only commits that day were some "CppMicrosServices" changes see http://cdash.mitk.org/viewUpdate.php?buildid=137878
Can this be linked to the build error?
I get the impression that somehow the compiler changed which this dart client was using. Before the build failed I think GCC was used and then somehow changed to CLANG. We changed the dart client script this week so that GCC is used again but we forgot to delete the cmake.driver and cmake.setup.
I already send Alexandra an email this morning and asked her to do that. Lets see if the dart client will still have problems.
Due to its severity, this bug is considered relevant for the upcoming 2012.09 release.
Please check the status and consider fixing this bug for 2012.09.
Yesterday I enabled OpenCV for the superbuild on my Mac Dartclient:
As you can see OpenCV built without any errors. Ingmar you think we can close this bug or should we try this for the remaining mac dart clients?