If it's solved, Please set it to "Solved" from unsolved.

@ed-wright

Not sure, but probably you have to do a "nmake distclean" in between or it finds your license information. However, this is the opensource forum. You would need to approach the commercial, they have to able to give the proper answer.

Super good work.
Thanks for updating on the way. will be helpful for others.

What version of Debian are you currently using ?

@koahnig

SetName takes in a char* because it is a part of an API.

@kshegunov

Here are the relevant linker calls. I don't know how to get the .pro file from a VS project.

Here is the linker call in the project that makes the dll:

/OUT:"E:\Users\misappsci\Documents\Projects\yyy\x64\bin\yyy3D.dll" /MANIFEST /LTCG:incremental /NXCOMPAT /PDB:"E:\Users\misappsci\Documents\Projects\yyy\x64\bin\yyy3D.pdb" /DYNAMICBASE "sl_zed64.lib" "opencv_world310.lib" "cudart.lib" "kernel32.lib" "user32.lib" "gdi32.lib" "winspool.lib" "comdlg32.lib" "advapi32.lib" "shell32.lib" "ole32.lib" "oleaut32.lib" "uuid.lib" "odbc32.lib" "odbccp32.lib" "qtmain.lib" "Qt5Core.lib" "Qt5Multimedia.lib" "Qt5Gui.lib" "winmm.lib" /IMPLIB:"E:\Users\misappsci\Documents\Projects\yyy\x64\bin\yyy3D.lib" /DEBUG /DLL /MACHINE:X64 /OPT:REF /PGD:"E:\Users\misappsci\Documents\Projects\yyy\x64\bin\yyy3D.pgd" /SUBSYSTEM:CONSOLE /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /ManifestFile:"x64\3DRelease\yyy3D.dll.intermediate.manifest" /OPT:ICF /ERRORREPORT:PROMPT /NOLOGO /LIBPATH:"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\lib\x64" /LIBPATH:"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0/lib/x64" /LIBPATH:"C:\Program Files (x86)\ZED SDK\dependencies\opencv_3.1.0/x64/vc14/lib" /LIBPATH:"C:\Program Files (x86)\ZED SDK\lib" /LIBPATH:"C:\Program Files\boost\boost_1_63_0/lib/x64" /LIBPATH:"C:\Qt\5.7\msvc2015_64\lib" /TLBID:1

Here is the linker call for the project that uses the dll and has the run time error:

/OUT:"E:\Users\misappsci\Documents\Projects\Aerie\host_x64\x64\Release\AerieLib.dll" /MANIFEST /LTCG:incremental /NXCOMPAT /PDB:"E:\Users\misappsci\Documents\Projects\Aerie\host_x64\x64\Release\AerieLib.pdb" /DYNAMICBASE "Qt5Core.lib" "Qt5Gui.lib" "Qt5Multimedia.lib" "yyy3D.lib" "sl_zed64.lib" "opencv_world310.lib" "cudart.lib" "kernel32.lib" "user32.lib" "gdi32.lib" "winspool.lib" "comdlg32.lib" "advapi32.lib" "shell32.lib" "ole32.lib" "oleaut32.lib" "uuid.lib" "odbc32.lib" "odbccp32.lib" /IMPLIB:"E:\Users\misappsci\Documents\Projects\Aerie\host_x64\x64\Release\AerieLib.lib" /DEBUG /DLL /MACHINE:X64 /OPT:REF /PGD:"E:\Users\misappsci\Documents\Projects\Aerie\host_x64\x64\Release\AerieLib.pgd" /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /ManifestFile:"x64\Release\AerieLib.dll.intermediate.manifest" /OPT:ICF /ERRORREPORT:PROMPT /NOLOGO /LIBPATH:"C:\Qt\5.7\msvc2015_64\lib" /LIBPATH:"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0/lib/x64" /LIBPATH:"C:\Program Files (x86)\ZED SDK\dependencies\opencv_3.1.0/x64/vc14/lib" /LIBPATH:"C:\Program Files (x86)\ZED SDK\lib" /LIBPATH:"E:\Users\misappsci\Documents\Projects\yyy\x64\bin" /LIBPATH:"C:\Program Files\boost\boost_1_63_0/lib/x64/" /TLBID:1

Hi,

I haven't done any static compilation of QCA but there's a QT_IS_STATIC in the src CMakeLists.txt. Might be worth playing with it.

Hope it helps

Hi @Michael-R-LegakoL-3com-com,

I think a better approach, is to use a macro to apply the dllimport/export, and then enable that macro in the library only.

For example, if you look at qmake's simple_dll test example, the simple.h header contains:

#ifdef SIMPLEDLL_MAKEDLL # define SIMPLEDLL_EXPORT Q_DECL_EXPORT #else # define SIMPLEDLL_EXPORT Q_DECL_IMPORT #endif class SIMPLEDLL_EXPORT Simple { ... }

Then the simple_dll.pro file contains:

DEFINES += SIMPLEDLL_MAKEDLL

So, this way, when the library is being built (via simple_dll.pro), then class is dllexport'ed. But when other code uses that same header (in doesn't define SIMPLEDLL_MAKEDLL) then that same class is dllimport'ed instead.

Typically, you end up doing this sort of thing to many classes in a single library, so rather than having the #ifdef ... #define ... etc in each header file, it often ends up being written once in a "global" project header of some kind. For example, Q_CORE_EXPORT gets defined in qglobal.h, then used throughout all of the exported core Qt class headers.

Also see:

When creating a library with Qt/Windows and using it in an application, then there is a link error regarding symbols which are in the library

Cheers.

@SGaist
yes all opencv files is included in the path.
After some research in log file, i think I have a problème with the génération of libopencv_imgcodecs310 and libopencv_imgproc310 files.

I'll keep you posted.

I think problem coused from dependent dev libraries...

sudo apt-get build-dep qt5-default

solved the problem..

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.

As it turns out, I needed to add the "QtQuick" and "QtQuick.2" folders in the same directory as my *.exe file.

This wiki page brought me on the right path.

For some reason things disappear after the dollar signs in my posts so if you are interested in helping and need the CMakeList.txt file, you need to download the project from the link in my first post.