Qt 6

@bisoftmm , this might be an incompatibility with the many compiler options you set. To debug this further, can you try to strip down the command line to the bare minimum (i.e. leaving out all the -Wxyz , -Wno-xyz options)?

Is that compiler line by a build system?

We are use non-standart DEVRANDOM_WAIT at OpenSSL configure, so we are also should configure access right to this is device.

For the recommended steps, see also the Porting to Qt 6 Guide. Most people report that the porting effort was small, but that of course depends a lot on your code base ...

Feel free to reach out here though if you have issues with specific cases!

Thank you all.
Problem solved.

Owh okay, I got it, I had to add initializeOpenGLFunctions(); in my glwidget::initialize()

Could you provide full log and also what build-tools and Target SDK versions used?

@liteyear Thanks for your comment. One thing I should have mentioned in the original post is that I also need EGLFS_brcm plugin support for my specific usecase. However, it says TODO as below. I would like to know whether EGLFS_brcm plugin support is part of Qt6 enhancement plan or not.

qtbase/src/plugins/platforms/eglfs/deviceintegration/CMakeList.txt
if(QT_FEATURE_eglfs_brcm)
# add_subdirectory(eglfs_brcm) # special case TODO
endif()*

@Christian-Ehrlicher thanks! I was using Qt6 and also had Qt5 installed to support QSerialPort. The cmake was able to handling including the Qt5 libraries. :) Anyway, i'll be reworking my cmake to just use Qt 6.2

I got this working in 6.2.3 recently. At first I was tripped up by the qrc path. Note that if you have something like:

qml.files = $$files(*.qml) qml.prefix = /qml fonts.files = $$files(fonts/*) fonts.prefix = / # will automatically get directory name "fonts" as prefix RESOURCES += qml fonts

in your .pro file, then Qt will expect to find qml files in the top-level directory, but their qrc path will have a "/qml" prefix. On the other hand it will expect to find ttf files in the fonts subdirectory, and still need to be accessed using a "/fonts" prefix.

So with the /pro above, this works for me in main.cpp:

QFontDatabase::addApplicationFont(":/fonts/Arial.ttf"); QFontDatabase::addApplicationFont(":/fonts/Arial Italic.ttf"); QFontDatabase::addApplicationFont(":/fonts/Arial Bold.ttf"); QFontDatabase::addApplicationFont(":/fonts/Arial Bold Italic.ttf");

returning 0, 1, 2 and 3 respectively.

Also remember to clean your build before re-building, because the qrc resource files might be pre-built by qmake.

PS. I'm not recommending anyone distribute Arial with your app. Do you own legal research.

What about QImage::Format_Indexed8 ?

But you still should check the return values of prepare() and exec() and print out the error string when there is an error.

Okay, so maybe, this is actually a bug or not implemented yet. I'll create a minimal compatible example (which is quite easy) and file a bug report.

Thanks for the feedback!

Edit: Here you are: https://bugreports.qt.io/browse/QTBUG-101877

You're welcome ! Please don't forget to set the status as resolved. Thanks !

@dongkyu
Take your source which you say works in 5.10.
Try compiling it under Qt6. Maybe it will work first time, who knows.
Fix any errors, warning or issues. Read through Porting to Qt 6.
Unlikely to affect you, probably, but keep an eye on https://www.qt.io/blog/porting-from-qt-5-to-qt-6-using-qt5compat-library, https://www.qt.io/blog/porting-from-qt-5-to-qt-6-using-clazy-checks.

What's wrong with my comment 'don't use uint but char32_t as data type'?
Well, nothing! It's just that I did not realize that the QString::fromUcs4() was still there...

Thanks a lot!

@dcoup said in Qt v6.2 open source kit for macOS on M1:

That ticket seems to refer to Qt v5.15. I'm looking for a macOS M1 installer for Qt v6.2.

The ticket says that Qt 5.15 is used to build the installer. You use this installer to install various versions of Qt.