Qt Creator and other tools

Hi and welcome to devnet,

That looks rather like a bug.

Did you already check the bug report system for something similar ?

I have solved this problem by installing the same version of qt creator in the original directory and then uninstalling it

@surfcius , @Christian-Ehrlicher
In my code as pasted, Creator 13 I think (unless it's 11?), clang code completer too, I do not get that warning in the IDE. I don't believe I have touched any clang settings, I suspect my C++ is C++17. Why do I not get it?

https://bugreports.qt.io/browse/QTCREATORBUG-32191

@Perdrix
Yes, I think message

qt.qpa.xcb: could not connect to display

is the clue. I think that when xcb fails to load, their misleading message about libxcb-cursor0 notwithstanding, you get an explicit "failed to load" but not "could not connect to display". I think you only get that one when DISPLAY is wrong.

Hi @jsulm
Thanks for you response :-)

I think i have setup the sysroot correctly. In the "Preferences" -> "Kits" and under the Sysroot, i have defined:
/opt/fsl-imx-wayland/6.6-scarthgap-imx-full-image/sysroots/cortexa7t2hf-neon-poky-linux-gnueabi

@Jalim_Rabei Kits is a QtCreator thing. You just need to install Qt and in case you installed Qt for MinGW on Windows also MinGW. QtCreator will detect installed Qt versions and compilers and create Kits. You can modify these Kits or create new Kits by yourself if needed.

I can see it at https://bugreports.qt.io/browse/QTCREATORBUG-32176 Thank you.

Thank you. Please comment there with the details of the computer running. Memory, CPU, etc. Was the project using a remote device and so o.

I'm using Qt 6, MSVC 2022, qmake. I had to add this to the .PRO file:

QMAKE_CFLAGS += -std:c++17 QMAKE_CFLAGS += -Zc:__cplusplus

At https://stackoverflow.com/questions/29826101/how-to-restart-adb-manually-from-android-studio we learn that one has to do a:

$ adb kill-server && adb start-server

You could have this in a script that start Qt Creator, or in Qt Creator as an external tool.

Hehe. I've found the reason! My source tree contains a 3rd party library, which I updated recently. The new version would include an example showing how to use it with QML. Now, androiddeployqt is running qmlimportscanner with the root directory set to the source tree. Thus it will find this (unused) example code and stuff it's dependencies into the APK, nearly doubling the size.

I could get around that by specifying QML_ROOT_PATH in the project file.

You are right, the layout in "scrollAreaWidgetContents" solved the problem. Thank you very much.

@DeepakD Have you thought of this: USB-hubs need power, and especially on battery powered devices this may be a problem.

Are these tablets connected to a power supply are are they on battery?

Regards

@cristian-adam that link looks very promising. It looks like there are a few variations on the proposed solution -- any idea which one I should use?

I'm running on Windows 11.

EDIT:

Problem solved.

set NODE_EXTRA_CA_CERTS=C:\ProgramData\Netskope\stagent\data\rootcaCert.cer

Or perform the equivalent from the Windows app to set environment variables.

The standard installation of Netskope only seems to include files in .pem.enc format, so my IT guy had to give me the .cer file. But...it works!

Thanks to all who looked.

I think the problem is related to upgrade from QtCreator 14 to 15. In order to have the linguistic tools available I had to create the menu entries by hand as the screenshot

Screenshot_20241209_200544.png

I've found the lldb stops on SIGSTOP signal.
After command in debugger log view

process handle SIGSTOP -n true -p true -s false

lldb runs ok on thread starting - it doesn't break anymore.

However I don't understand how to add this command to run automatically on the start of debugger. Nor "Additional startup commands" not file ~/.lldbinit didn't help.

I can put this command into Debugging Helper Customization text box. In this case command works - however regular breakpoints don't work :)

This happens when, on example of OpenSUSE TW, Qt updates. New Qt version with new documentation makes records in ./config/QtProject/qtcreator/helpcollection.qhc. And after each update of Qt in helpcollection.qhc make new records about new documentation versions that points to the same *.qch files in system /usr/share/doc/qt6. So removing helpcollection.qhc solves this issue. I guess this is a QtCreator's issue, because removing in settings dialog old documentation versions doesn't work, they appear again and again after restart of QtCreator.