Qt Creator and other tools

@cristian-adam encode works on strings, str or QString. decode works on bytes, bytes or QByteArray. That may explain <unavailable> on text().decode(). I told you I didn't understand :) If you had stuck to Hello world! we wouldn't be having this discussion ;-)

@JonB said in QtCreator installer/app poisons the Win11 registry: @cristian-adam Is it the case then: the uninstall either does nothing or does not work, the reinstall does not really uninstall/remove but just happens to overwrite retained values with something else so it ends up working OK? I know I can't be that much use as I don't do Qt under Windows. But would you like me to go find where the Uninstall script is stored in registry so you can try it out standalone, or do you already know this? See above at the manual removal script. I think the Qt Installer should be able to reproduce and fix the QTIFW-3944 issue. I see @ziller is still assigned, hmm.

@Gerd-Brecht Please have a look here: https://forum.qt.io/topic/164022/unable-to-create-bug-report-on-jira Ps: You can now post faster Regards

You can write a script starting all your applications and add a "Custom Executable" run configuration pointing to that script in the "Run Settings" of your project.

@cuijg I'm not totally sure if this is a bug or a feature, but for me the warnings go away if I use the Trash bin symbol in the Issues pane: [image: 40424c4f-f1ac-448c-9b98-a79ff2fcb4c4.png] Regards

@Taupter Have you selected Project > Run Settings > Run in Terminal? That is a per-project setting. Regards

Oh my, didn't know this was a thing! I assume these settings are lost/not usually part of a versioning system? @Alex-To do you use cmake? I use this function in cmake: function(copy_dir TARGET SRC_REL DEST_REL) add_custom_command(TARGET ${TARGET} POST_BUILD COMMAND ${CMAKE_COMMAND} -E make_directory "${DEPLOYMENT_PATH}/$<CONFIG>/${DEST_REL}" COMMAND ${CMAKE_COMMAND} -E copy_directory "${CMAKE_CURRENT_SOURCE_DIR}/${SRC_REL}" "${DEPLOYMENT_PATH}/$<CONFIG>/${DEST_REL}" VERBATIM ) endfunction()

@shyney7 Thank you for highlighting this issue. I have created a bug report on your behalf: https://qt-project.atlassian.net/browse/QTBUG-144585 If you find any other issues, please report it directly to our bug tracker like the link above. You can log in using the same Qt Account that you use to log into this forum.

@cristian-adam said in Qt creator no qDebug() output in debug mode - Qt 6.10.2: For Qt Creator 19 I've made sure that lldb would work when Run in terminal is set. There is an update for Qt Creator 19 final, all debuggers on Windows will get the QT_WIN_DEBUG_CONSOLE=attach environment variable set for the running programs. This means that if you have the checkbox Run in terminal, you will get the qDebug() output there. cdb or lldb! This is for console and WIN32 applications. It simply works! ™️

That was it - thank you!

To build the project on the build device you need to open the project from the build device, not a local project. In contrast to Docker support, Qt Creator doesn't do any magic mapping there. You can open projects from the device with File > Open From Device, the device is accessible with the "f" (file system) filter in Locator (and starting with QtC 19 the device root is also accessible in File System view).

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.