Qt Creator and other tools

Nope, simply using the maintenance tool to get the sources, is not enough. I still get assembly stuff if I debug into library code such as QTimer. Ok, I can now see the sources, by doing this: Tools->Options->Debugger->General->Add Qt Sources... and selecting /home/me/Qt/5.14.1/Src which results in: Source path: /home/qt/work/qt Target path: /home/me/Qt/5.14.1/Src

Hi, I think the simplest would be to remove MSys from your PATH environment variable.

@Mozzie said in Is the documentation of qtcreator out of date?: but when i followed the symbol to the header of QLayout, this function is not marked as deprecated. That's understandable. As @Christian-Ehrlicher said, QLayout::setMargin() was deprecated in the header in Qt 5.13. (This was done by Christian, by the way -- thanks for helping to maintain Qt!: https://codereview.qt-project.org/c/qt/qtbase/+/251052 ) However, it was marked "obsolete" in the documentation since the very start of Qt 5.0: https://code.qt.io/cgit/qt/qtbase.git/tree/src/widgets/kernel/qlayout.cpp?h=v5.0.0#n348 (probably even earlier) In this case, the header and the documentation were out-of-sync for a long time.

It's not the same python version between the screenshot and the current code.

@marcelpetrick Then you should file a suggestion at bugreports.qt.io/QTCREATORBUG (and add a link to the report here). Regards

Are running this on two different computers (or VMs)? It seems there are more variables involved than just 'different version of QtCreator'. Working: Qt 5.12.2 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 8.3.0) on "xcb" OS: Ubuntu 19.04 [linux version 5.0.0-38-generic] Environment: QT_ACCESSIBILITY="1" QT_AUTO_SCREEN_SCALE_FACTOR="0" Not Working (note, QT_ACCESSIBILITY is not set): Qt 5.12.4 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 9.2.1 20191008) on "xcb" OS: Ubuntu 19.10 [linux version 5.3.0-40-generic] Environment: QT_AUTO_SCREEN_SCALE_FACTOR="0" Do you have additional KDE packages (not sure what that the 'kdedev' folder is) installed on the one that's working? Does your application depend on them? Can you run it in debugging to see where exactly it is crashing?

@aha_1980 ok，thank you！

Can you please share the solution? I am facing the exact same problem, but with gstreamer-1.0, as I posted here: https://forum.qt.io/topic/112301/gstreamer-1-0-not-found-on-mac Thanks!

In the installatiopn are some plugins missing.

Update on this: it turns out that there were some artifacts from a prior version of Qt that caused make to look at/use incorrect locations for some files. I blew away the directory and re-cloned. Here are my condensed notes on how to accomplish this (note that this is for a static build): 1. $ git clone https://code.qt.io/qt/qt5.git 2. $ cd qt5 3. $ git checkout v5.14.1 // or whatever 4. $ perl init-repository or $ git submodule update --init --recursive 5. $ configure -confirm-license -static -static-runtime -opensource -release -platform win32-g++ -opengl desktop -nomake examples -nomake tests -nomake tools -recheck-all -prefix c:\qt5\5.14.1\static 6. mingw32-make -j4 7. mingw32-make install // if a prefix option was specified in configure Thanks to everyone for the help on a frustrating issue.

@matone1 and how is this issue related to Qt framework?

After further testing, the issue isn't the "run in terminal" setting. Instead, it seems that if I'm using the QtQuick/QML stuff, then QtCreator reports the following: 11:16:51: Starting /tmp/QmlTest/bin/QmlTest ... 11:16:51: Application finished with exit code 0. i.e. it runs, but exits immediately, with no error code. If I then ssh into my target and manually run the same binary, I see the expected output on the screen, and it doesn't exit until I kill it with ^C. I don't see this issue if I run an QtWidget application. The C++ launcher for the QmlTest application is below. The contents of the QML file doesn't seem to matter. #include <QGuiApplication> #include <QQuickView> int main(int argc, char *argv[]) { QGuiApplication app(argc, argv); QQuickView *view = new QQuickView; view->setSource(QUrl(QLatin1String("qrc:/main.qml"))); view->show(); return app.exec(); }

@HendrikGerloff I know, maybe my structure is something legacy but it works fine for my jobs... also qt-creator using this for qmake... for the future I am going to use only cmake

I found an alternative to this, i simply defined my constants in a Js lib (.pragma library) instead of QML Singleton // Consts.js .pragma library property string darkBlueColor: "#005490" property string lightBlueColor: "#006BB7"