Bugs on Mac - Yosemite

Hi,

I'm using opencv.3.0.beta on a MAC Yosemite 10.10.2 and so far it mostly works, but there are some challenges that should be adressed:

Really I don't like this cmake or at least this cmake port for the Mac. Somehow cmake is using the wrong headers and I don't see how I can do in cmake the simple equivalent of a "-I/usr/local/include/myDir". I did a trick to make it work at all, but I would prefer to do a real solution. Any suggestions someone ?
The highgui module has some real fancy problems:
the screen resolution is obviously 1280x800 in opencv instead of the 2560x1600 I paid for and I don't see, how this can be set (at least there is no simple cmake property).
the waitkey doesn't seem to work. For me this looks like the window does not get the focus and so it is impossible to grab keys. There is no way to manually set the focus. Please add a setfocus call to this window stuff.
All the window properties don't seem to work at all p.ex. WINDOW_AUTOSIZE does not autosize etc. I solved this by scaling myself, but I would prefer not to...
In general I don't understand the module structure of opencv. I mean most of the time I can guess it from the names, but many times I had to grep it from the headers and once or twice I had to use symbols to find it. I would suggest to just get rid of this structure, just make one library. Even on Smartphones this shouldn't be a problem any more...

20029 ●16 ●82 ●207 http://stevenputtemans...

Let me promptly reply to this, since I see you are full of frustrations

OpenCV3.0 beta is like you can read a beta edition. It is known to still contain tons of bugs and people, core devs and volunteers, are trying each day to get it sorted out for the major release of 3.0. Grabbing the latest master branch from Github is way more interesting, since you get all those free fixes!
Considering the port to the MAC using CMAKE, it is quite straightforward and people love to use it. Can you point out which wrong headers are being used where so that we can fix it?
Highgui is one of the single modules that works like a charm on every single system here. Can you point out what is wrong?
waitKey does work, but it needs an active window. Just calling a namedWndow before it works. Do not forget to apply an & 0xFF when using it in Linux and mac, because they require it to push back the correct ascii value.
Most window properties only work if you built with Qt support, did you do so?
Modules have more benefits than you think, it enables people to build only what they need and to keep the memory consumpsion to a minimum. It also makes it more clear where to look for stuff.

I think you are quite negative on the OpenCV side, how can we make you feel better?

Comments

Sorry to make me look depressed, actually it mostly does what I want which is good I think ;-)

The problem is in the structure on the Mac, the official headers come with Xcode commandline tools. But if I use them in eclipse, the code analyser will paint my code red. So I prefer to use the ones that come with gcc, which work like a charm. But I can not mix the headers, which means that my code and opencv have to be compiled with the same headers or I get really "interesting" error messages. As I didn't find a way to use the gcc headers in cmake, I have to compile my code against the Xcode headers, which I don't trust.

BetaVersion ( 2015-03-11 10:21:34 -0600 )edit

Sry I have to split my comment:

According to the cmake documentation there is a include_directories() property, which is supposed to be something like -I directive, so somehow this might help to be added...
This might be in the setup, I have build spring boot (=Java) application for the Tomcat that uses highgui only for debugging via JNI O_o. But it looks like the window does not get the focus, so it does not get any keystroke events nor correct window scaling
see 3.
sorry no Qt here
I'm not convinced, the problem is that it is sometimes really hard to figure out the correct properties, include files and libraries. So you might want to take a closer look at the documentation...

seems to be some automatic numbering in place...

BetaVersion ( 2015-03-11 10:23:22 -0600 )edit

Completely out of my league there. Afaik you simply build OpenCV yourself and header files are far from IDE or system specific ...
- Add what? What do you want to include in OpenCV as extra directory?
- Aha the java interface and jni - again out of my league here, im focussing on C++ interfaces
- The documentation is build identical to the modules, so that makes it easy in my eyes and many other programmars out there. It is still very unclear what you would desire there.

StevenPuttemans ( 2015-03-12 06:00:29 -0600 )edit