Qt Creator and other tools

Hi, same thing with QtCreator 16. I will create a bug report. Thanks

So, with the beautifier we made it work now. In the end we had to remove LineEnding: CRLF From our .clang-format file, since this was breaking completely the formatting in Qt Creator. Running clang format from the command line worked fine though. The ClangFormat extension does not apply the formatting on the full file, but only on changed lines, which we did not want. Also it made the settings dialog of Qt Creator extremely slow somehow.

I figured it out. Interestingly, cmake was not selected on the Qt installer by default. I had to install cmake through the Qt Maintenance Tool and then select the cmake version on the Qt6.8.3 default kit. I find it very strange that it was not installed by default. Tricky tricky... [image: 78e30105-f2e7-49d8-8376-956f4c182a88.png]

@Yuyang I suggest you upgrade your QtCreator and MinGW versions, because you're using quite old versions.

@unknown_error I do not use Windows/MSVC/CDB so cannot answer any deeper than this, but it is a "first chance exception". That is an MSVC debugger thing and should be ignored --- you are not interested in any first chance exceptions which occur. Try unchecking that First chance exceptions checkbox? Does the debugger actually stop at that breakpoint? In which case you will just have to continue from there. I do not know if you can permanently ignore it.

Thanks! after reinstallation it really works

@cristian-adam Thanks! That's really helped me

@Willer75 The pretty printers heavily depend on the internal memory layout of the objects, and this layout changes at least on major upgrades like Qt5 -> Qt6. Sometimes, while fixing code for newer Qt versions, the printers break for older versions (unfortunately). So what you could try is to use the latest Creator version 16.x, and if that does not work you could file a bugreport. Regards

@PetQter Can you please explain what is this feature when qtcreator tries to build automatically something immediately after start ? In previous crashes I saw git process there, so qtcreator tries to download something from git and build it on background. What is this feature for ? This is most likely not the case. As @jsulm already said, Creator needs to check the tools it is using, and the compiler and git are tools it is using. Regards

Hi and welcome to devnet, Looks like you are missing the OpenGL dev package for your distribution.

@JonB thank you, I will try

Understood. Thanks

i use Wayland, i switched to x11 like an hour a go into an x11 session (yeah, i have x11 also), and nothing, now i don't know if i'm missing a pkg EDIT: also my DE is KDE Plasma, and I tried the Flatpak version, same.. Google's AI, thinks that this could be: ~~To use Qt Creator with Wayland on Arch Linux, ensure you have the necessary packages installed, including qt6-wayland or qt5-wayland, and set the QT_QPA_PLATFORM=wayland environment variable. Here's a more detailed breakdown: Install Qt Creator: Use the package manager pacman to install Qt Creator: sudo pacman -S qtcreator. Install Wayland support for Qt: Install the appropriate Wayland plugin for your Qt version: For Qt 6: sudo pacman -S qt6-wayland. For Qt 5: sudo pacman -S qt5-wayland. Set the environment variable: To force Qt applications to use Wayland, set the QT_QPA_PLATFORM environment variable: Open a terminal and run: export QT_QPA_PLATFORM=wayland. To make this change permanent, add the line export QT_QPA_PLATFORM=wayland to your shell configuration file (e.g., ~/.bashrc, ~/.zshrc). Troubleshooting: If you encounter issues with Qt applications finding the Wayland plugin, ensure that the necessary directories are correctly copied or symlinked, as described in this Qt Forum thread. If you are using a custom Qt build, make sure that the Wayland plugin is included in the build. If you are using XWayland, you might need to set QT_QPA_PLATFORM=xcb to run Qt applications on XWayland. Wayland and Qt: Wayland is a display server protocol that aims to replace the X Window System. Qt provides the Qt Wayland Compositor module for developing custom display servers based on the Wayland protocol. The Qt Wayland Compositor module provides QML and C++ APIs for developing custom display servers. ~~ i have all of that i just need to run qtcreator under that env var, and see if that can solve it followed the ai steps, nothing also.. just that now the qt icon is not missing everytime i run a project in the window but that's all, didn't really worked at all

WSL is my friend - this worked for me. Thanks to everybody for your help in this thread. Now to try and create something :o)

Same on one of my PCs (on another one it does deploy these DLLs). I don't think these DLLs should be needed for my project, and I call windeployqt with the --no-system-d3d-compiler, shouldn't that prevent it from deploying this dead weight?

I was able to resolve this issue by adding CMake to the PATH (I'm on Windows), I could then update the Kits configuration to include CMake, and the project could then be built. I ran through the installation/getting started tutorial and that was not mentioned.

Remove the Qt version from the Kit. It's obviously wrong.

Still looking for solution but have yet to found any. As I mentioned above it is just posts about vintage QT Creator version. Any help would be greatly appreciated.