Installation and Deployment

Suspected cause The problem appears to be caused by this code in Qt Android accessibility: QJniObject rangeInfo( "android/view/accessibility/AccessibilityNodeInfo$RangeInfo", "(IFFF)V", rangeType, min, max, current); The constructor signature "(IFFF)V" is not available on Android 10 runtime. The call creates a pending JNI exception: java.lang.NoSuchMethodError but the exception is not cleared before continuing, which results in SIGABRT. Proposed fix The RangeInfo constructor usage should be protected by Android API level check. For example: if (QtAndroidPrivate::androidSdkVersion() >= 36) { QJniObject rangeInfo( "android/view/accessibility/AccessibilityNodeInfo$RangeInfo", "(IFFF)V", rangeType, min, max, current); if (rangeInfo.isValid()) env->CallVoidMethod(node, m_setRangeInfoMethodID, rangeInfo.object()); } or alternatively Qt should use the correct API availability check for RangeInfo constructor.

Hi, With which compiler ? Which configure parameters did you use ? What number of cores are you using at the same time ? What are your machine specifications ?

@Taytoo said in Are CVE patches pre-applied to the sources of older versions as well?: if I download the latest sources of the affected version (e.g. 5.15.19). Would they have the CVE patches applied already? No, the sources of Qt 5.15.19 remain exactly as how they were released back in May 2025 (https://www.qt.io/blog/commercial-lts-qt-5.15.19-released ). You'll need to apply the patches manually or upgrade to a version that already contains the patch.

Then I would check the cmake bug tracker to see if there's something related there.

I edited socketcanbackend.cpp to include the missing include file (<linux/sockios.h>) and compiling is proceding...

I want to complete toolchain qt creator cross compile for ARM_64 my host is x86_64 and cross compile for ARM_64 khadas bord.

Hi and welcome to devnet, Which version of the Maintenance tool do you have ?

I figured it out... Thanks... It was just a syntax problem...

@flashmozzg Hi, unfortunately you need to do a fresh install. We'll look into improving this particular case.

That's a generated script in the build folder. It's called automatically for you. If you want to see its content, there are hidden folders in the build folder.

@Poornesh said in Patch Application Failure on Yocto Zeus + Qt 5.15 Due to Source Revision Mismatch: Dear Qt Support Team Please be aware this forum is for users of Qt. It is not read by The Qt Company. My limited understanding is that Qt for Yocto is part of "Boot to Qt" (https://doc.qt.io/Boot2Qt/b2qt-customization-requirements.html)? If that is true I believe this means you must have a commercial license for The Qt Company? And if that is so then, although you are welcome to post here and await any user answers which might come, you may have to contact TQtC for your issue?

@MSDev said in Disclosure of Application Source Code under LGPL v3.0: So if I do dynamic linking then I don't have to share my source codes right? In addition to what my colleagues have said. Since your code is in PySide/Python rather than C++, how do you propose not to "share your source code" anyway? Unlike the C++ situation your Python files are required at runtime and are perfectly readable to anyone. Unless you do some sort of "obfuscation" or you can force somehow to compile the Python you won't be supplying any "object" files of your own anyway?

Hi, Glad you found out and thanks for sharing the solution ! You can close the thread yourself by using the Topic Tools button or the three dotted menu beside the answer you deem correct :-)

@DinoNZ said in Installing Qt Automotive Suite : Qt Automotive Suite option not available: Is it possible to get an Open Source license for QT Automotive Suite? I'm a private individual not a company so am just looking at the open source trial versions for now. Qt Automotive Suite was based on Qt 5.15. It is no longer being maintained or offered, but its source code is open: https://doc.qt.io/QtAutomotiveSuite/qtas-install.html#build-from-source (it is basically a "bundle" of multiple modules that are relevant to the automotive industry) For a modern automotive solution, see Qt for Android Automotive: https://www.qt.io/blog/qt-for-android-automotive-6.11-released https://doc.qt.io/QtAndroidAutomotive/qtaa-overview.html

I've just come across exactly the same thing on Mageia. Has been driving me nuts! My ini file was identical to OP's.

@udobyk hi and welcome to devnet, Please open a new thread showing the exact errors you are getting. In between, you have the dependencies listed in the Linux chapter of Qt's documentation

Looks like a bug, I've reported it here: https://qt-project.atlassian.net/browse/QTBUG-145563