3rd Party Software

check this repo: I've made a fork for this repo to make it work with Qt6
https://github.com/pourjour/qsqlcipher/tree/main

@UserNotFound just remove second Q_DECL_IMPORT from smtpmime_global.h :

#ifndef SMTPMIME_GLOBAL_H
#define SMTPMIME_GLOBAL_H

#ifdef SMTP_MIME_LIBRARY
#define SMTP_MIME_EXPORT Q_DECL_EXPORT
#else
#define SMTP_MIME_EXPORT
#endif

#endif // SMTPMIME_GLOBAL_H

Found the solution. Added this to the end of the function and now it the partitions filesystems are correctly formatted:

newBootFs->create(*rootReport, bootDeviceNode); newRootFs->create(*rootReport, rootDeviceNode);

Also I could delete this:

if (devicePartitionTable->typeName() == "gpt") { qDebug() << "Setting partition type for GPT table"; newBootPartition->setType("C12A7328-F81F-11D2-BA4B-00A0C93EC93B"); // GPT GUID for EFI System Partition newRootPartition->setType("0FC63DAF-8483-4772-8E79-3D69D8477DE4"); // GPT GUID for Linux Filesystem } else if (devicePartitionTable->typeName() == "msdos") { qDebug() << "Setting partition type for MBR table"; newBootPartition->setType("0xEF"); // MBR type code for EFI System Partition newRootPartition->setType("0x83"); // MBR type code for Linux Filesystem }

Hi,

WARNING: I am NOT a lawyer.

AFAIK, nothing forbids you to create such an application. That said, designer already exists and is language agnostic since it produces only an XML file that is consumed by uic. uic that is able to generate Python code. Also, if memory serves well, there's a new project file for Python projects that helps automate code generation so you might be missing on that for your projects.

It works. Thanks again.

@rzucca have you already seen https://github.com/INNO-MAKER/usb2can/tree/master/For Windows/QT/QT/QTInnoMaker ?

That looks like an useful example for you.

Regards

Good !
Then please mark the thread as solved using the Topic Tool button or the three dotted menu beside the answer you deem correct so other forum members may know a solution has been found :-)

You can use it the same way it's done for the Qt libraries in your cmake file.

@Aman55

Qt version is not set in the Kit You should use CMake provided by Qt Online Installer In the screen-shot there is yellow exclamation mark, but the message is cut, check that also

@Aman55 Yes, you need to look at the stack trace pane in the debugger when that happens, so that you know where it comes from.

Hi Slandino, I started working a few days ago on a project to mix Qt and flutter. I have already some working code, but it's using offscreen buffers (my final objective is to make a plugin to have a flutter layer in OBS) so I've not even looked on how to render to a window context. But the code may still work for you. I've commited the mess of code I wrote so far to https://github.com/hefsoftware/temp_qt_flutter (it compiles on windows, at least for me). Hope it will give you some help.

@JonB Hi these I have already included.
Also, I have seen a few examples at Github. I have tried to compile with MSVC as well as MinGW.
These are the errors:

moc_india_map_test.obj:-1: error: LNK2001: unresolved external symbol "public: static struct QMetaObject const QgsVectorLayer::staticMetaObject" (?staticMetaObject@QgsVectorLayer@@2UQMetaObject@@B) moc_india_map_test.obj:-1: error: LNK2001: unresolved external symbol "public: static struct QMetaObject const QgsRasterLayer::staticMetaObject" (?staticMetaObject@QgsRasterLayer@@2UQMetaObject@@B)

after I try to run the project.

Same issue, I have also got this cmake warning:

-- qmlplugindump failed for org.kde.quickcharts. -- Could NOT find org.kde.quickcharts-QMLModule (missing: org.kde.quickcharts-QMLModule_FOUND) The qml plugin 'QuickChartsplugin' is a dependency of 'project', but the link target it defines (KF6::QuickChartsplugin) does not exist in the current scope. The plugin will not be linked.

All passages was good and well done .... all error reported become from bad ram stick only. Change it and all work.

@3n3l said in TUIO multi-touch:

Got it working, the issue was that my sending application would be in focus and then my qml application would not receive touch events when being out of focus (What?).

I've been bitten by that issue category. Using a virtual machine that won't know it has lost focus from the physical input hardware is another solution, although not as convenient as the environment variable.