@JonB Thanks, I normally use CQTDeployer. That would mean for other projects the DLLs also need to be added under LIBS in the .pro file ?

@SGaist Great Thank you this, I know that qt has its own MQTT module just I had already developed my code for MQTT using the mosquitto library before I knew I was going to be making a GUI using QT.

Yes, I solved it. I don't remember how I installed it but strangely my installation missed ONLY this qhelplink.h and QHelpLink. How strange!

They both seem like dead projects, nothing you can rely on.

grassator/react-qml last commit was Dec 15, 2017
only 1 contributor, only active 4 years ago.

ongseespace/react-qml last commit was Mar 26, 2020
had 2 contributors, most active 3-4 years ago.

As you may sensed for the extremely few amount of responses before and considering that ReactJS is since many many years one the most prominent JavaScript library in the world, mostly top 1 (https://2021.stateofjs.com/en-US/libraries/front-end-frameworks). It looks not to be in the priority of the Qt strategy.

Looking at the architecture of Qt, they seem pretty much incompatible. Qt is a complete stack with a complete e2e experience. Where you don't want to mix other stacks or other frameworks.

That also means, I think, you cannot for example create QML based components that are reusable in other frontend stacks, where the backend may be anything else. QML are closed components.

So, in other words no support for Web Components specification: https://www.webcomponents.org/introduction
which was created to be able to produce reusable components.

If anybody, disagrees or have more insights, happy to know about it :)

@JonB sweet Jesus on the bike... this is the dumbest typo I ever made.

I am so embarrassed atm.

Thank you :D

If doStuff() is not const, then don't declare d pointer as const:

Q_D(myClass) // NO "const" here! d->doStuff();

Yes @JonB, it requires depencencies but this is not a problem. I will install this automaticly after users choice.

You can find them under:
LTS RELEASE
https://dotnet.microsoft.com/download/dotnet-core/3.1

Current release
https://dotnet.microsoft.com/download/dotnet/5.0

Note: .net CORE works with Linux, macOS und Windows.

@jsulm
thank you really much - now i can really start to learn/write :D

Are you trying to move things around in the folder where you are currently doing the application deployment ?

@Opa114 Thanks for the feedback. So please mark this topic as SOLVED now.

@JonB well, I thought it just creates a new build file for the new compiler (which it does), but I have to admit my understanding for compilers is not very deep.

gcc...
So if I got that right, you just configure and manually run the same qmake binary to output for different platforms and then use the generated makefile in the parent makefile project or optionally one step earlier call qmake from the script (but generally not still one step earlier and...)?

@SGaist I wish mean throw this message : QEventLoop: Cannot be used without QApplication

But this problem is no more. I have delete the project and create un other without dll...
It's not the best solution but it's gona work.

No need for another thread, I got it working. Here are the android related package versions which finally made it to work in case someone else has troubles:
0_1540840385190_4fa02fd1-7668-4c41-a244-2537d0fb3016-image.png

The latest JDK and NDK didn't work.

I hope they fix the name strings for the next beta. It's annoying and confusing to have "GCC" everywhere even though it really uses clang.

As an option, you can create a separate thread in your DLL, e.g. QThread. Then, create the QSerialPort and then move it to that thread... Maybe it will help... An idea is that QSerialPort should get a QThread as a parent.

AFAIK, it is not simple to use the Qt classes in the separate DLL's. It belongs not only to QSerialPort, it belongs also to other QIODevice and other classes. e.g. that classess can use the QTimer internally, which does not work without of an event loop... So, it is hard... I have not ideas.

@JScars Please try binaries from http://download.qt.io/snapshots/ci/qtwebkit/qtwebkit/qtwebkit-Windows-Windows_7-Mingw53-Windows-Windows_7-X86.7z

You're welcome !

Since you have it working now, please mark the thread as solved using the "Topic Tools" button so that other forum users may know a solution has been found :)

@VRonin Thanks!