> I've managed to compile qtuiotouch > (https://github.com/dancasimiro/qtuiotouch/) on OS X (10.8.4, ftr) using Qt > 5.1.0 by applying some changes to its CMakeLists.txt file > (btw, not in Dan's repo yet, you can have a look at it on mine > https://github.com/Morpheu5/qtuiotouch/ and bear in mind that I've > also changed the MODULE at the end to read SHARED because it was making a > shared object (.so) file and not a dinamically linked > library > (.dylib) like the ones I've seen among Qt's own plugins.
I think that plugins are supposed to have the "so" suffix on Mac OS X, but I am not sure. I don't have a mac handy right now. > Then, as per Dan's instructions, I went ahead and compiled his demo > application, and instructed Qt Creator to run it with arguments - > plugin TuioTouch. I then fired up my old faithful TUIO emitter, which I've > successfully used before in other contexts, and watched the > whole thing fail miserably. > > I then modified the cli arguments to include the actual path of the > libqtuiotouch.dylib file because that TuioTouch looked suspicious all > alone. After all, the file sat in its build directory, how in the world would > my application know where to look? It still failed. I then > proceeded to make a symlink inside Qt/5.1.0/clang_64/plugins/ and reverted to > using TuioTouch instead of the full path. Still nothing. The plugin has to be in a subfolder named "generic" (i.e. Qt/5.1.0/clang_64/plugins/generic) for Qt to find and correctly load it. The folder should already exist and contain the plugins for mouse and keyboard handling. You will have to copy the plugin manually. I haven't tried to make cmake handle that aspect yet. FYI, you can set the QT_DEBUG_PLUGINS environment variable to get diagnostic information about plugin loading. ~Dan
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
