Hi, do you get the same error if you try a vanilla Hello World python app?
Say like this:
app = QApplication(sys,argv)
window = QWidget()
window.setWindowTitle('Hello world')
window.setGeometry(100, 100, 640, 480)
window.show()
sys.exit(app.exec_())
Hi, one way stop your app from exiting, you could try showing a message box, for example like this:
...
app = QApplication([])
alert = QMessageBox()
alert.setText('Click me when lsof -c is done')
alert.exec()
...
then you should have time to do a lsof -c englauncher
After a lot of head scratching I found that if I install from a mirror as documented at https://wiki.qt.io/Online_Installer_4.x#Selecting_a_mirror_for_opensource then the installation worked perfectly well.
Is the file on the default server corrupted or something?
Anyway, I hope someone finds this useful if they have a similar problem.
@SGaist I have to move on as this is getting me no-where. If I ever need a chart I'll use a third party one. This should work in QT Creator (the latest one that I downloaded recently), it should be a simple case of checking a box, but it just doesn't work....possibly a bug in the software (...or a feature).
Hi, paraview works because is using it's own Qt (version 5.9.1).
On the same PC you also have Qt version 5.12.8 and 5.12.9 installed. Having more than one version of Qt installed on the same computer is always risky :.-(
Try to get rid of that qt5-default Qt version 5.12.8 and instead install complete versions of flameshot and gnuplot (so that they get also get their own, internal Qt version, like paraview has now).
Hi,
@kunalkokare said in Qt Automotive Suite:
Can someone please give me clarity on what to use below components for ?
Qt for Device Creation
To build applications for embedded devices (embedded can range from a small IoT device up to an ATM)
Qt GENIVI Extras Module Reference Documentation
Qt IVI Module Reference Documentation
As silly as it may sound, it's the documentation of the respective modules
Qt Application Manager
As the name suggests it's an application manager. It allows you to create more complex applications that includes multiple process/window on embedded system.
Qt QmlLive
Live viewer for your QML code
Reference UI (Neptune)
Reference UI implementation for Qt in In-Vehicle Infotainment (IVI) systems.
GammaRay
Qt application deep inspector.
For this error
error: The deployment device "Redmi Note 7S" does not support the architectures used by the kit.
The kit supports "armeabi-v7a", but the device uses "".
you need to turn OFF the USB debugging mode from your mobile once and again turn ON it.
For this question
how can i check the target android SDK version of this project ? means
on which SDK version use this project.
You need to go into the project tab in Qt from left pane. then select your android kit. then go into the build tab. into the build tab click on the Details of the Build Android APK. and in this there is one field Android build platform SDK: in this field you can see the SDK API Version.
FOUND IT:
in CMake set_target_properties I added the line:
WIN32_EXECUTABLE true
couldn't have found it without knowing it was a terminal window.
Thank you.
Ugrade to a recent Qt version or apply this fix: https://code.qt.io/cgit/qt/qtbase.git/commit/src/corelib/text/qanystringview.h?id=813a928c7c3cf98670b6043149880ed5c955efb9
If you do not want to upgrade you should take a look at https://bugreports.qt.io/browse/QTBUG-89977 - there are other fixes for gcc11
@sierdzio I guess I was short sighted after a booster shot. I thought the submodules should be in a separate category but they were not. They were in the installer. Thank you for your answer!
LoL, I already solved it.
And this is how I solved the issue. My PATH is clean and nice, however, my cmd's AutoRun is a mess. I tried deleting everything in AutoRun (HKCU\SOFTWARE\Microsoft\Command Processor\AutoRun or HKLM\SOFTWARE\Microsoft\Command Processor\AutoRun) for testing and Qt was able to build fine.
My AutoRun is messy because I integrated cmder into cmd but didn't follow the author's guide. I stuffed a long script into AutoRun (without creating a separate 'cmder_shell.bat' file) and it was working fine before I started using Qt. And now I see the above issue I mentioned.
Hope my stupid experience helps those who face similar issue to have more solutions. For those who use cmder integrated into cmd please follow the author's guide, don't be like me.
@andr Thank you! I know I've seen that link before but couldn't find it.
If those Qt5-flavored builds of Qt Creator keep coming, that'll solve almost all of my issues with Qt and Windows 7, except if I want to build and test a Qt6 app. In that case my patches above could still be useful :-)
For the people who face the same issue as me:
I found the solution for this issue.
We need to set QML2_IMPORT_PATH environment variable to qml dir in qtdeclarative component by running: export QML2_IMPORT_PATH=/path/qt5/qtdeclarative/qml before running make check.
@jsulm
Hello,
Yes I did. See the dir qmake.exe /s which does a recursive dir for the qmake.exe in all the sub folders of the current folder.
As you can see it did work as it did find the qmake.exe version in the mscv2019_64 directory and mingw_64, but nothing was found in the msvc2019_arm64 folder.
I continued digging in the folder and I also notice that there is no windeployqt.exe in the arm64 folder.
Cyrille
@hskoglund Thank you for clarifying that.
Thanks to that i got on the right track. Assuming that libqxcb.so was missing because the option -qt-xcb was dropped was a mistake.
I found this thread https://github.com/bincrafters/community/issues/1229 that showed me that i might miss a dependency. As proposed i have added the -xcb option when calling configure. It showed a few failing tests.
I was not able to find a log for those tests but the config.log showed that "test config.qtbase_gui.libraries.xcb_util" was failing due to a missing xcb-utilh. While this was none of the tests i was looking for it made me check if all of the requirements mentioned at https://doc.qt.io/qt-5/linux-requirements.html are installed. None was missing, so i did some guesses.
Since there none "dev" variants are on the requirement list i have installed:
libxcb-render0-dev
libxcb-util0-dev (due to similarity in name i assume that this fixed the missing xcb-util.h)
and since a pthread test was failing i installed
libpthread-stubs0-dev
Now libqxcb.so is generated when building Qt. I conclude that the official requirements list for Qt 5 is missing at least one package.
My problem is solved. This thread may be closed.
@Christian-Ehrlicher Installing the latest win 10 SDK didn't help so I've updated that bug report with the extra info. Thanks for the pointer; that bugreport didn't show up in my search results.
@JonB Sure. I did not find anything, beside a bug in Qt 5.15.0-5.15.2 that should have been fixed 6 years ago. And, as I mentioned, it works on my developer machine with the exact same Ubuntu version.
@Quorn-Julio
dont use cmake-gui.
simple execute (in a build directory, can also be a new folder):
<QTDIR>\bin\qt-configure-module <module-src-path>
cmake --build .
it already takes care of everything
Post Scriptum:
I did download the NDK, but when I try to select the folder, I get the following error:
There is indeed no RELEASE.TXT file in the directory, but there is a source.properties.
The path is: C:\Users\cydeb\AppData\Local\Android\Sdk\ndk so it seems valid.
There is a toolchains sub directory in this folder.
This is still a problem in 2022 in building Qt 5.12.12 for Odroid with Mali support. Minor improvement to @Ignacio_Alvarez 's answer is that SONAME should include the major version, so --set-soname to libGLESv2.so.2.
@UltraBlack_
Please search again for your error message, which is qt.qpa.xcb: could not connect to display. There are plenty of posts about that on this forum and elsewhere. As I wrote earlier that means:
Not an xcb library loading problem, rather however your X display is set up/connecting.
Since you say it runs under sudo, I can only imagine either your permissions or your X environment is set up to allow that but not for your non-sudo user.
As always, try to run an xterm. If you cannot run that you know you do not have a Qt problem.
