Qt Creator and other tools

@Christian-Ehrlicher said in Project Tree: Source and Headers Inconsistent View: Don't use absolute paths for your source files in your project. I am not. Both source and headers are specified in EXACTLY the same way, but one is being displayed with the absolute path and the other isn't. That said, in fixing an unrelated problem, I had to re-create the project file (changing from cmake to qmake). This fixed this problem and now both show relative to the project directory. It doesn't explain why it was doing that, but since I won't be switching back, it doesn't matter for me.

@cristian-adam It seems this part checks if the library is called "Qt6Something" and adds the Qt bin installation directory to the path for the next iteration of the function.

Are you planning on using F5 inside a console application? Then change the project settings to open your app inside a separate terminal window instead of using the Qt Creator logging window.

Looks like you'll have to do some symlinking to get things up and running. See https://github.com/llvm/llvm-project/issues/55575

@chava What did you install? How? And on what platform?

Thanks! Changing to Xorg seems to be the trick.

Also the shortcut Ctrl+L, which is standard in terminals for clearing the screen.

Qt Design Studio is meant to use its own "internal" kits, and is not meant to "Link with Qt" outside. This bug will be fixed in the next release: https://bugreports.qt.io/browse/QDS-9933

I switched to MSVC and now debugging is great again (with cdb)

@Aleksandr-Tarasov No idea, it doesn't make much sense. Try running the gdb from a terminal quite outside of Qt Creator, does that work?

@qbullshitq I had different experience from yours: with "qt" I started to love it from second one when I decided to look at this. Why did you want to clone Qt from a repository? You can install it simply from an installer. Do some research on it before you touch something. Or post your problems in the forum and people here will help you out. Your life will be much easier.

@JacobNovitsky This hurts so much, I hope to receive any support

When you want to use the operator !=() you have to provide it - a compiler can not simply create the operator!=() from the operator==().

@cristian-adam I have never used vim, i think it's horrible, why would anyone use something like this in the first place 😅. It would be nice to be able to configure this behaviour is QtCreator. I think it's logical for the pointer to stand after the word when moved, considering the space is a character, it should not be skipped.

@ocgltd Although I suspect it will work, you should just test gdb /your/executable in a terminal to make sure gdb is fit for purpose.