Qt Creator and other tools

i think this is a bug so i just reported it on the jira. here is the bug track page for it: https://bugreports.qt.io/browse/QTCREATORBUG-29841 if anyone else has this issue, i found a workaround to fix the problem, and it's listed on that page.

Same here. @adonezid did you find the reason?

@oin-oin Check here out. https://forum.qt.io/topic/151244/online-installed-android-qt-6-6-but-build-requires-newer-version/6?_=1698687184749 34 is the latest for Android 14. Better to know your target Android version(14, 13, 12, or 11...) first.

@Omar-Hatem No

I just tested this on macOS with Qt Creator 11.0.3 but with Python 3.9.6 and it started successfully.

@Isaac-DeJager First match in Google: https://github.com/probonopd/linuxdeployqt

Remove the files qwindows.dll.debug and qwindowsvistastyle.dll.debug from the respective folders, it works for me

@AnneRanch [image: 9b0bfc3c-f51e-47f3-b17c-2bcdc029999f.png] I assume you mean (without writing it explicitly) Qt Creator and debugging in Qt Creator. If a proper debug build is run with the debug function, you should see something like the screenshot attached. The lower part is the stack trace. Clicking on a line gets you to the caller. Doesn't need to be enabled.

@jchirkes said in Using Qt in on an external Server: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" Is X11 running on your machine? To get more information about why xcb plug-in could not be loaded set QT_DEBUG_PLUGINS env variable to 1 in the terminal where you're starting your app, then start your app and check the output in the terminal. See https://doc.qt.io/qt-6/debug.html

@JacobNovitsky qmake Variables Your flags will be compiler specific

@Veit said in QT quick emulation layer crashed: @JonB iSorry was not aware about that. If my post violates the etiquette here, I will of ourse stop posting, Of course not! You are welcome to post here! I meant only as I said: this looks like a possibly "difficult" one, or might be specific to you, so I just hinted that you might find you can call on TQtC if you need to for this. I don't even know if they would help, but maybe with an evaluation license they would be keen to :)

@Veit said in QT creator 11.0.3 issues with loading project: @sierdzio thanks for the hint. Be aware that I am currently evaluating so I do not now much about CMakeList. I just create a new project, save it, restart the Creator and load a created *.qmlproject file. I assumed this is the project file. Is this my mistake? What can I load instead? CMakeLists.txt located in root folder of your project is the main project file.

@Redman I also could not find any documentation about it. Perhaps you can suggest this as feature request? https://bugreports.qt.io/secure/Dashboard.jspa

It's mostly a tooling and operating system bug. See https://bugreports.qt.io/browse/QTBUG-117413 Qt Creator is creating a CMake project in such a way that will get result in long paths. CMake then gives this paths further to ninja / make and then to the compiler. GCC has this bug https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107974 and even though is an easy fix to add the manifest entry required by Windows ... nobody has fixed it yet. Visual C++ has the same issue, see https://developercommunity.visualstudio.com/t/compiler-cant-find-source-file-in-path/10221576 The only compiler that's fine is Clang. Ninja also requires a build from latest sources, since https://github.com/ninja-build/ninja/releases doesn't list yet version 1.12.0 which has the one line manifest entry that enables long paths. I usually say just switch to Linux or macOS, they are way more friendly to developers, and issues like this are non existent. Or ... just use c:/dev to have short paths 🙂