Qt 6

@NullByte said in Qt 6.2 Mobile Development:

hello i found the solution Qt 6.2.0

QT += core quick

#include <QJniObject>
#include <QJniEnvironment>
#include <QCoreApplication>

QJniEnvironment::
QJniObject::
QNativeInterface::QAndroidApplication::

I think look so cool

Thanks for sharing!

By the way, the blog post has been fixed. If you want some features that are not part of QJni* or QNativeInterface, the correct header is <QtCore/private/qandroidextras_p.h>

That is certainly a good solution for others with this problem, but I'm using Qt as a vendored dependency with add_subdirectory and system CMake in a project of mine, so that solution doesn't work for me.

I've marked the topic as solved, as there is now a solution for my use case and others.

@timob256 said in Qt not go glut :(:

$$PWD/../../../../../../../usr/lib/x86_64-linux-gnu/

Are you really sure this is correct? Use absolute paths for system libs.

@Osama-Adel Please add Android SDK Command-line Tools, it is required to enable android build with QtCreator

@Dariusz said in Qt 6 fails to load jpg in to QImage:

Do you know whats the name of plugin or dll?

imageformats\qjpeg.dll

https://bugreports.qt.io/browse/QTBUG-96073

Hi I solved this by reinstalling Qt Design Studio.

What if you do the build on the command line ?

@VRonin said in Qt6 regression with QAbstractListModel? Type argument of Q_PROPERTY or Q_DECLARE_METATYPE(T*) must be fully defined:

I would have thought the include guard on the header already took care of this but I might be wrong

No it's not cause I've several Models using it. They all need it for their moc compilation. But then their headers are included in the main object ClementineRemote that is where there is the redefinition.

I also just ran into this issue - ninja will delete the TS files when "cleaning" (e.g. when being invoked via cmake --build . --clean-first).

Seems weird that it would touch anything in the source tree.

@SGaist Yeah. I still had to make other changes to get things to work but they were specific to us. I think it must have been the order in which I made the changes that made this seem necessary when they weren't

@Stokestack said in Is Ninja installed with Qt 6?:

I did find the following here:
"We recommend to use CMake's Ninja generator. This is also configure's default."

That's talking about building Qt, not building user projects.

Scroll down lower in the article: "Once you have installed Qt, you can use CMake or qmake to build your projects."

Ninja is not a requirement.

Not sure when configure is invoked, however.

configure is the script that starts the Qt build process.

There is no configure script for your own projects.

why didn't I get a complaint when opening it in the earlier Qt Creator, and also not when I opened it again in the current one?

I don't know.

Update us if you can reproduce the issue -- otherwise, there's not much else we can say or do.

@Stokestack said in QT SerialPort not found on QT Maintenance Tool:

Underneath that there is a 5.15.2 directory, but there's also a lot of important stuff that's right below "Qt" and not under the 5.15.2 subdirectory.

Look closely closely at my screenshot. That is my "Qt" folder.

It's the same as yours, but it has both "5.15.2" and "6.2.0".

And it seems like stuff that would clash with (or be overwritten by) a newer version:

Don't worry, the things in next to 5.15.2 will not get overwritten if you run MaintenanceTool.app.

(They will only get overwritten if you run the original installer, which you are not supposed to)

void QGridLayout::addWidget(QWidget *widget, int fromRow, int fromColumn, int rowSpan, int columnSpan, Qt::Alignment alignment = Qt::Alignment())

gridLayout->addWidget(graphicsView, 1, 0, 3, 1);

Thanks for that reply. That doesn't quite make sense though. Why can you create a single-level project and have Creator build you a CMakeLists file then?

With CMake becoming the native build system, I would expect Qt Creator to offer the same functionality it does today. That means (among other things) letting you create a "subdirs" project, which would add add_subdirectory to CMakeLists. Why doesn't it simply do that? What happens when QMake goes away?

I don't see how Qt can competitively proceed into the future if its IDE doesn't even let you manage your project. Furthermore, it's a huge missed opportunity to clarify CMake usage and expose its many functions in an orderly UI.

Apologies for false alarm....
It was crashing trying to set style sheet to a non existent plugin...
Issue resolved..
Thanks for the help :)

@laseranichris OK. You can report this in Qt bug tracker.