Qt Creator and other tools

first let me preface that i am new to using cmake - so maybe i'm doing something stupid. when i clone the master - and import - my configure project screen shows only a number of ci and debugging kits to select from). if i unselect them all - then the configure project button is disabled. if i select one (which i think is wrong) - it fails (but i am not interested in these debugging/tracing kits). when i download a recent earlier version then (via zip file - i get the same problem i then got a much earlier version 2.11 (by downloading a zip). when i imported it then i do get the standard kit selection choice - where i can select the one with my compiler and qt version - and cmake lruns however, it won't build ( i think because its looking for older versions of qt - 2.11 is five year old).

@MHMart_asc No, always ignore "first chance exceptions" when debugging under Windows.

This topic was also present as a bug report at https://qt-project.atlassian.net/browse/QTCREATORBUG-33741 Which I've fixed, and with Qt Creator 19 things would simply just work out of the box with lldb.exe.

Let me just bump this. I have the same question and am in general not clear about the command/mapping mechanics. One more example (of several) I don't get: I assigned the "Ex Trigger Expression" rb to Rebuild project and i can type :rb - but it always builds without cleaning. In contrast, when I select the same corresponding menu item (mouse click), it does rebuild with an initial cleaning step.

I have solved this by defining everything under the "build" folder in the different *.pro files. It seems that if a subproject is configured individually, i.e. outside of the SUBDIRS project, whatever configuration is overridden by the SUBDIRS main project configuration. I put the "TEMPLATE=lib" subproject files into the "3rd_party" folder. The only drawback is then that the different Makefiles.* and .qmake.stash files used in building the libraries are also generated in that folder which is under source code management. However, these can be ignored by the SCM by applying the corresponding settings necessary for ignoring certain files.

Thanks @ziller @aha_1980 @J.Hilk for your suggestions. I decided to do a full backup of my machine first. Then I realised that my project's config and current state data-files had probably been damaged when my Qt Creator got wiped by Qt Maintenance Tool. So I set about finding out how to recover those files as well as my original Qt Creator (version 15.0.0, installed Nov 2024) - from backup. Google AI was quite helpful, as long as I took its advice with a grain of salt, as I usually do. Apple's Time Machine utility was even more help, as I cherry-picked the files and folders I needed to restore. That all went well, except that I had an obsolete 'ui_mainwindow.h' file (generated by Qt), which would not compile. I hacked my way around that and am back in business now. My app is working fine again. It is full-screen by default and does not really need a complicated KDE-style main window.

I figured out the problem. When I installed Qt 6.10.2, I selected "Qt/Build Tools/LLVM-MinGW 17.0.6 64-bit" but not "Qt/Qt 6.10.2/LLVM-MinGW 17.0.6 64-bit". So it was trying to link my LLVM-MinGW project with the MinGW version of libQt6EntryPoint.a.

@Programist I have a patch for this under review: https://codereview.qt-project.org/c/qt-creator/qt-creator/+/713439

@cancech Thank you for the follow up!

I've compiled Qt Creator (master branch) from sourced. Add few prints in CustomParser and ... none of them it triggered/printed. You're right - some other parser blocks my custom parser. PS: This still doesn't change the fact that given WARN isn't displayed on Issues pane.

Seems yet another account in yet another service is the only way to go. I'll post my report in the bug tracker and solve this one.

My bad. PATH not correctly configured, cmake couldn't find the compilers. Issue resolved after pointing PATH to compilers installed along with Qt Creator.

thanks @cristian-adam, i created a bug report.

@cristian-adam I've made a new breakthrough here: I suddenly recalled the experience of locating problems through Windows' system logs when I used to check project anomalies, so I tried to look for answers in my system logs. Surprisingly, at the same time as my Creator's anomaly, there were large-scale system errors. The error process came from the Windows background program backgroundTaskHost.exe, and the source of the error was an unconnected HP printer. I consulted an AI, which told me that when Creator uses Designer to open a .ui file, it scans all connected devices on the computer in full. Coincidentally, the driver or cache of this device of mine might have had some abnormalities, causing a failure in the access of Devices-AccessBroker, and then repeatedly accessing this non-existent device, resulting in a large accumulation of memory usage. Even after I tried to delete the device from the Device Manager, the anomaly was still triggered. Now I'm trying two things: disabling Creator's full device scan function and completely removing this annoying virtual device from my computer. I will try every method I can find and also hope you can give me some more professional advice and help. Thank you very much! [image: f08becec-18f1-4ec4-ad01-6fa64d1685a2.png]

I'll do that! Thanks for the pointers