use macro: Q_IMPORT_PLUGIN(QLinuxFbIntegrationPlugin);

What does adbshield_plugin_import.cpp contain ?

Hi, Do you mean that if you build with MinGW-32 it's all working fine but not with MinGW-64 ?

Whew! I think I got it... The mistake was to use the includes of shared \build_dev when building in release. There is only one little difference which made everything work: qconfig.h! It defines QT_STATIC in the static \build_app1 ... The debug config of the project created by the Qt Add-in has to be adjusted a little though: Include directory $(QTDIR$)\include =>...\build_dev\qtbase\include. Lib directory $(QTDIR$)\lib =>...\build_dev\qtbase\lib. The project still uses \build_app1\qtbase as Qt Version. That way, the Debug build looks for includes and libs in \build_dev while the Release build looks in \build_app1. And the .lib symlinks are not necessary anymore, I just kept the bin directory symlink. Just in case someone else wants to do something like this...

Another interesting development: I tried running on another machine with the Qt toolchain installed, and the program worked. So it appears it is still reading something from the filesystem that is not on a regular Windows machine, but I don't know what that might be. I did package all the qmldir files needed for Qt Quick to work.

But this time, I have a different error: /home/kumararajas/ti-sdk-am335x-evm-07.00.00.00/linux-devkit/sysroots/i686-arago-linux/usr/bin/../lib/gcc/arm-linux-gnueabihf/4.7.3/../../../../arm-linux-gnueabihf/bin/ld: /home/kumararajas/Integrate_UI/G-CPU/lib/libuicorelib.a(uicontroller.o): undefined reference to symbol '__cxa_begin_catch@@CXXABI_1.3' /home/kumararajas/ti-sdk-am335x-evm-07.00.00.00/linux-devkit/sysroots/i686-arago-linux/usr/bin/../lib/gcc/arm-linux-gnueabihf/4.7.3/../../../../arm-linux-gnueabihf/bin/ld: note: '__cxa_begin_catch@@CXXABI_1.3' is defined in DSO /home/kumararajas/ti-sdk-am335x-evm-07.00.00.00/linux-devkit/sysroots/i686-arago-linux/usr/bin/../arm-linux-gnueabihf/libc/lib/arm-linux-gnueabihf/libstdc++.so.6 so try adding it to the linker command line /home/kumararajas/ti-sdk-am335x-evm-07.00.00.00/linux-devkit/sysroots/i686-arago-linux/usr/bin/../arm-linux-gnueabihf/libc/lib/arm-linux-gnueabihf/libstdc++.so.6: could not read symbols: Invalid operation collect2: error: ld returned 1 exit status make[4]: *** [bin/FireApp] Error 1 make[3]: *** [libraries] Error 2 make[2]: *** [libraries] Error 2 make[1]: *** [libraries] Error 2 This looks like standard library compatibility issue. Any thoughts on this?

Found it in /qtbase Nevertheless some modules were not compiled. I'm missing qtwebsockets, the Makefile is also missing. It worked just fine for Win32 platform. Any ideas?

@Lays147 Hey! How does your app looks like?

Thank you. I'll be subclassing text/combo/check boxes as well.

@SGaist thanks , I have actually compiled without the script no errors thought while compiling, but I'm not sure if the errors will popup when i start using the build, but it would be really useful for future builds also I'm compiling OpenCV , so here is my installation paths : DirectX SDK : C:\Program Files\Microsoft DirectX SDK (June 2010) Microsoft SDK : C:\Program Files\Microsoft SDKs MSVC : C:\Program Files\Microsoft Visual Studio 12.0 .NET : C:\Program Files\Microsoft.NET OpenSSL : C:\OpenSSL-Win32 Qt source : C:\Qt\5.4.1 thanks again for your time

@SGaist Ok, thank you so much!

I suppose I got it sorted by adding an -ldl flag in the FlightGear compile. Strangely enough, the first time I tried it it didn't work at all. I tried it again and it magically worked. Now I'm going to be building/rebuilding for the next several hours just to figure out how exactly I fixed it...

Solved add to .pro : CONFIG += plugin static QTPLUGIN += qtslib qevdevkeyboard qevdevmouse qevdevtablet qevdevtouch Run (active all input device): $./test -plugin tslib -plugin evdevmouse -plugin evdevkeyboard :-) Static Plugin

add -tslib and recompile qt and chart example but not solved ! ./configure -prefix /opt/installed/arm/QtEmbededd-5.4-static-tiny210/ -opensource -confirm-license -no-xcb -xplatform linux-arm-gnueabi-g++ -nomake examples -feature-THREAD -feature-CONCURRENT -feature-SOUND -feature-EFFECTS -no-openssl -lpthread -optimized-qmake -no-cups -qt-zlib -static -qt-libjpeg -qt-libpng -qt-sql-sqlite -qpa linuxfb -linuxfb -tslib export TSLIB_FBDEVICE='/dev/fb0' export TSLIB_TSDEVICE=/dev/touchscreen-1wire export TSLIB_PLUGINDIR='/usr/lib/ts' export TSLIB_CONFFILE='/etc/ts.conf' export TSLIB_CALIBFILE='/etc/pointercal' export TSLIB_CONSOLEDEVICE='none' export TSLIB_TSEVENTTYPE='INPUT' export QT_DEBUG_PLUGINS=1 cat /dev/touchscreen-1wire | hexdump 0000000 0fff 0fff 07c6 8629 07c5 8626 07c5 8626 0000010 0fff 0fff 0966 85bb 096c 85b9 0968 85a8 0000020 0968 85a8 0fff 0fff 0964 85ba 0938 85a9 0000030 08ba 8571 085d 8559 07a1 8573 0736 8599 $chartthemes -platform linuxfb -plugin tslib QIconvCodec::convertToUnicode: using Latin-1 for conversion, iconv_open failed QIconvCodec::convertFromUnicode: using Latin-1 for conversion, iconv_open failed QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.2" since plugins are disabled in static buils QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QPlatformInputContextFactoryInterface" since plugins are disabled in static builds QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QGenericPluginFactoryInterface" since plugins are disabled in static builds QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QStyleFactoryInterface" since plugins are disabled in static builds

@SGaist Thanks. Now I have a more clear picture about signals.

Well, I tried compiling the source from scratch with a fresh source, and it works like a charm for some reason. Problem Solved.