@rechtsanwaltsteyer:
Sorry for the late answer.
I always compile cb-trunk myself very frequently on Ubuntu, arch and, from time to time, on Pi-Os as well. The trick is, that I also use wxwidgets-trunk. At least in the past, the wxwidgets that came with Ubuntu was outdated. Building wx is even easier than cb. I install wx in /opt so that it can coexist with the one that comes with the distro and on which other installed packages may rely on. For cb and wx I use simple makefiles. The make targets for cb, wx (and other programs) are identical. Chained in the shell, a full rebuild is triggered with one single command (re-call) via Ctrl-r. Instead of a ppa I install both on Ubuntu as debian packages via checkinstall. Simpler to use than ppa.
I posted the relevant contents of the makefiles a long time ago in this forum. If you want, I could pm the relevant makefile parts to you.
With the recently added clangd-client I started to use code-completion again. The old one I had switched off for years.
Independent from that client, I also use clang-tidy directly from cb as an added "compiler". Like with usual compiler warnings, clicking onto one warning jumps to its code location.
btw: Thank you for the german translation.
