Qt Creator and other tools

Hi, I think the FILE macro is not the best way to find your main.cpp file since it usually skips giving you the full path to the file. For the MSVC compiler you can try the /FC compile switch

I have prodded the wizard some more and found the following: If you take the above config and remove the Debug Configuration it successfully created the project. (Although there's some issues when compiling) Setting the build system to "CMake Project for Qt" always fails with "Object reference not set to an instance of an object." once a linux target is selected The with the project created for WSL Visual Studio complains that this is targetting WSL1 and that the QT Installation path isn't set correctly So yeah I guess I'll have to this very diffently than expected

@Qreator35 Hi, You might want to give a bit more explanation about what is happening. The screenshots might be out of order or you are showing that you have progressed between different errors. etc. Please add details.

@HansKottmann said in qDebug() is not working anymore in QT-Creator (Installed from QT-Installer from QT.io, OS: Manjaro Linux: The only thing I've changed is the args QStringList, it looks now exactly like yours, the only difference are the quotation marks at the beginning and the end of the file path string because filenames can have white spaces: I already explained earlier that you are calling errorString() too early. So did @jsulm . And what to do about it. Your Unknown Error currently does not indicate anything has gone wrong. You need to change your code. Your understanding of whitespace as it appears when you type a command into a shell versus how to pass arguments to spawned processes is not right. The arglist should be as a wrote and not have quotes. Or send the whole command line to bash -c.

Moved the 'QtCreator and other tools' as this is a question on QtCreator debug output even though OP did not mentioned it.

Upgrade to QtCreator 19+ with the known fix, or move the build folder from a shared folder (vboxsf) to a local disk (ext4) inside the virtual machine, perhaps because the problem is related to I/O against a shared folder with Windows, and not to the QtCreator version itself.

@Jennise-Hall said in Qt desktop app crashing at startup: @SGaist LOL useful information though. Agreed ! :-)

Download from qt.io/download-qt-installer-oss (not the generic address) and log in with a new/clean Qt account that has not previously been linked to a commercial or trial license.

Hi again, in the meantime our clang experts are working on a solution for using lldb. I'm sure they will do it well. I still have another issue with lldb. But therefore I will start another thread or even create a bug ticket. And for the issue with gdb not showing the object member values (which was my original one) I first will try to find out, whether there is a new gdb version doing it better.

Hello, you can have multiple executables in one CMake project, and deal with it in one single Qt Creator instance. As a template you can git clone "https://codereview.qt-project.org/qt/qtqa" and load .../src/fuzzgen/CMakeLists.txt in Qt Creator. It's a project with multiple executables. You can select the run target like that: [image: aa73058f-e72b-45f2-9e27-b532d2583f5e.png]

Not that I want to discourage you but did you consider using Qt Multimedia ? It already provides support for playing music using ffmpeg under the hood. That said, did you already check the mpv C client api ?

Hi, Which version of Qt Creator ? Which version of Qt ? On which OS ? Does it happen if you use a default project ? Is it a complex class ? Do you have a more complete error message ?

I have similar issue, working on a fairly large project. When build completes and VS is about to launch a debug instance. The process freezes for 5-10 seconds. I'm also getting repeated warnings from Visual Studio that the extension caused VS to become unresponsive. Previous Qt Vs Tools version was working fine.

A question: How is this integrated. Uses it the full codemodel for the project (I have 140000 LOC) or looks it only the corrosponding CPP-File what should be fast ? I will check the other hints.

@cristian-adam I think I'll write a suggestion for an additional "Build current executable only (disable other build targets)"

This is not a Qt problem, more details. Qt creator feature request here.

I never thought I'd have to add the current folder (.). That solved my issue indeed.

@cristian-adam Ah, yes, that did the trick. Thanks!