Qt Creator and other tools

The error occurs because the auto-setup script created by QtCreator (build/.qtc/package-manager/conan_provider.cmake) cannot determine the current C++ standard. Take a look at the function function(detect_host_profile output_file). The error is fixed by moving the C++ standard setting to the very beginning of your CMakeLists.txt script, before the project keyword. For example, the correct CMakeLists.txt: cmake_minimum_required(VERSION 3.16) # it is important that the standard be defined before the project keyword set(CMAKE_CXX_STANDARD 20) set(CMAKE_CXX_STANDARD_REQUIRED ON) project(i18n_strict LANGUAGES CXX)

@Pl45m4 thank you for the reply. I have found the set(CMAKE_TRY_COMPILE_TARGET_TYPE "STATIC_LIBRARY") context here. and yes using msvc for opencv usage was chatgpt`s suggestion.Im very new to this. By initial parameters do you mean mingw and ninja?

First peak at the Chat functionality in #llama.qtcreator. I used it to talk to gpt-oss 20b to create me a qt c++ chat widgets application that chats with a llama.cpp server using its json api. See how it went at ... https://youtu.be/qWrzcx6QhOA

Thank you !

Reinstalling Qt didn't helped, but I noticed that QtCreator settings remained unchanged Renaming forlers C:\Users\%username%\AppData\Local\QtProject C:\Users\%username%\AppData\Roaming\QtProject resolved problem, Qt created new pure settings, and debugging runs

These JSON files should not have to be modified. There is something wrong with the desktop configuration.

Hi, use "depends = ..." in your qdocconf file to make qdoc aware of the Qt index files it should use to resolve the links to the Qt classes, and point qdoc to the path were it finds these with the -indexdir command line option. Documentation: https://doc.qt.io/qt-6/22-qdoc-configuration-generalvariables.html#depends Usage in Qt Creator developer documentation: https://code.qt.io/cgit/qt-creator/qt-creator.git/tree/doc/qtcreatordev/config/qtcreator-developer.qdocconf#n48

@jeremy_k , @JKSH , thanks for your comments and observations. some good food for thought. I think this query can now be regarded as solved, since the originally proposed solution works.

same issue with QtCreator 15.0.0 and 17.0.0 on Windows 11 using either KIT 6.4.1 MSVC 2019 64bit or 6.9.1 MSVC 2022 64 bit quite problematic isn't it?!? how come oO can't debug properly anymore without @cristian-adam workaround... (on Windows)

@icebergenergy Let the QtCreator devs know via mailing list or implement the functionality yourself and submit the patch via gerrit or github.

@JasonWong you can join the Developing Qt with Agentic AI webinar. [image: 27fc6cf1-d5d8-4d87-99a1-ef3790e1e78e.jpg] I don't know if there is a Q&A section, but if there is, you can ask the question above.

Is this the same crash as https://forum.qt.io/topic/163072/unexpected-crash-when-using-custom-delegate-in-qcombobox ? Whatever OP might expect, it should not crash Creator if it does that!

@CrazyCarrot I think the SO guy was falsely imagining or confusing with VS! Without getting into it, I found VS had more features in it than Qt Creator. It is just possible that Creator's Message box, which I believe appears for the "tracepoint", passes that on "raw" to the underlying debugger, so perhaps some gdb syntax for it would work with gdb debugger or if there is any equivalent for MSVC, but I don't know and wouldn't hold my breath.

I know this is an old thread, but someone might find this helpful: (Qt Creator 17 on Mac) Press Cmd+T for the selection dialog. Once it pops up, hold Cmd and press T to cycle through your open projects. Release Cmd and the selected project is activated and the dialog disappears. Note: The dialog has three columns Project, Deploy, Run. For the above to work the column Project has to be active (dark selection field there). It looks like that each time you start Qt Creator the active column will be Deploy. In that case just click once a project name or use arrow keys to activate the Project column, and from that time it should work again (until you quit Qt Creator).

@hackerturtle 00007635 5.66594458 [18472] qtc.projectexplorer.toolchain.msvc: readEnvironmentSetting: "call \"D:/Program Files/Microsoft Visual Studio/2022/VC/Auxiliary/Build/vcvarsall.bat\" x86" "C:\\WINDOWS\\system32\\cmd.exe /D /E:ON /V:ON /c C:\\Users\\21421\\AppData\\Local\\Temp\\QtCreator-UTRrUJ\\cwmuNx.bat" Env: 79 00007636 5.66596460 [18472] qtc.utils.process: Process 30 starting (blocking without event loop): C:\WINDOWS\system32\cmd.exe /D /E:ON /V:ON /c C:\Users\21421\AppData\Local\Temp\QtCreator-UTRrUJ\cwmuNx.bat 00007637 5.67927456 [18472] qtc.projectexplorer.toolchain.msvc: No updates for "Visual Studio Community 2022 17.14.36401.2 (x86)" It has to do with the Qt Creator's way of checking if the Visual C++ environment has been changed. This shouldn't trigger any pop-up, but something in your environment causes this behavior.

Indeed! As soon as I killed the adb processes, the freezes stopped immediately. Thanks a lot, you really saved my day!

@JonB said in Qt Creator editor: Can we insert a column of sequential numbers?: Purely ooi, why does it change from cardinal words to ordinal ones after SEVENTH? :) Because: @cristian-adam said in Qt Creator editor: Can we insert a column of sequential numbers?: This works with ... AI :))

I ended up cloning the latest version from github: git clone https://github.com/qt/qtbase then running cmake install with the cmake variables I need like vulkan

You need to update your gdb, not the whole toolchain. See https://www.qt.io/blog/mingw-and-side-by-side-manifests for details.