Vincent Chernin

In the 6.2.7 flatpak build app startup got a lot faster due to less gsettings activity, but I can still reproduce this.

Yes, I see the same `source_location` problem with clang-tidy here. What is weird is meson includes a `clang-tidy` target (which is very useful for CI) but it seems to repeat...

I seem to have made clang happy by switching `std::source_location` to `std::experimental::source_location`, and including `experimental/source_location`. Now the clang-tidy warnings make sense. There doesn't seem to be a way to suppress...

> it still seems to build normally with gcc with `std::experimental` Nevermind, this causes linking failure.

> We have to check the compiler and its version. I think it is alright since if the configuration is not correct, clang-tidy should fail in CI. I am not...

> But we would essentially just be telling if clang

I realized in #1739 I missed `std:source_location` is also in `util.cpp`... so while this fixes most of the errors there is no point merging a half done fix. I will...

> But the fact it does not use systemd is annoying when trying to start PipeWire. At least I was able to run pipewire from the build directory from within...

> At this moment all that the circleci profile is doing is compiling EE in an Arch Linux docker image and running ninja install after it. Yeah, which is already...

At least locally I managed to put together a script to run easyeffects (flatpak!) in podman with systemd and pipewire and dbus all more or less working. With this I...