Any concrete plans after the GDB BoF?

Joel Brobecker
Mon Oct 31 17:31:15 GMT 2022

> I would suggest mandating one version, and for that version to
> continuously be the latest stable version of clang-format, like we do
> for Black.  When a new version comes out, we don't have to wonder if /
> when we move the next version.  Someone just pushes a patch re-formating
> the code to the next version, if there are some differences.  It keeps
> the overhead to a minimum.
> So far I have never seen problems related to distro-specific patches, as
> we have seen with autoconf.
> For Debian/Ubuntu, it's easy to get the latest stable version through
>  I don't really know about other distros.  In any case,
> it's easy to build and not long (not long like building the whole
> llvm/clang):
> $ git clone --depth 1 --branch release/15.x
> $ mkdir -p llvm-project/build
> $ cd llvm-project/build
> $ cmake -DLLVM_ENABLE_PROJECTS=clang -DCMAKE_BUILD_TYPE=Release -G "Unix Makefiles" ../llvm -DCMAKE_INSTALL_PREFIX=/tmp/llvm
> $ make -j 4 clang-format
> $ make install-clang-format
> $ /tmp/llvm/bin/clang-format --version
> clang-format version 15.0.4 ( 08bd84e8a6358eb412fcef279f8875e2d69a3374)

Thanks for sharing, Simon. This makes the option of using this tool
very attractive.


More information about the Gdb mailing list