Adel Kara Slimane

Hello, enabling the `tools` use flag did not solve the issue. However, putting this in ` ~/.config/clangd` ``` CompileFlags: # Treat code as C++, use C++20 standard, enable more warnings....

> Can you confirm in Tools -> Options -> C++ -> Clangd that Path to executable is /usr/lib/llvm/14/bin/clangd and Insert header files on completion is checked? Yeah, it does not...

It works now, thanks for figuring it out ! A note: I cannot change the path for `clangd` in the settings to the one version 14, after restarting Qt Creator...

> If so, rebuild qt-creator and report if that resolves the issue. Weirdly enough, my configuration in the `~/.config` was borked, so I deleted it and all good now. >...

> I could continue editing this out but it may be accepted as a sys-devel/clang bug so I'll likely file a bug later and decide how to proceed. https://bugs.gentoo.org/853967 Haha...

Thanks for this great job! Could you reproduce the Wayland issue ? (I only tested under Gnome although I don't see why it should be Gnome specific)

Thanks for your answer! Good luck! > Btw, t[here](https://github.com/justanhduc/task-spooler/releases/tag/v1.3.0-cpu) is a tar ball for the cpu-only branch in each release (for e.g., here. Is it not what you need? I...

Hello @justanhduc, sorry for the late answer, I was busy with other projects ! :D Okay, I tried to compile master and unfortunately I cannot see a cmake toggle to...

You got me completely lost, where is this `mangohud-setup.sh` script ? What does it do ? How come something doesn't use the build system of MangoHud ?

Oh I get it better now, the script that installs from the binary tarball. The meson approach of this PR could be transferred there too: 1. Use `DESTDIR="$PWD/build/release" ninja -C...