Feature Request: Preserve original compiler name (for cross-compilation clangd compatibility)

[tadcoburnsonos]

Feature Request An option to bear (--preserve-cc-name ?) that causes it to preserve the original compiler name (and path, if any) in the compilation database.

Background I've been working to get VSCode and its clangd language server to work with compilation databases created by "bear". We are cross-compiling, and have discovered the following problem:

• clangd tries to run the compilation command it finds in the compile_commands.json file, but this fails for our cross-compilation case because the compilation database says the compiler is either "cc" or "c++", and that compiler doesn't understand cross-compilation options such as "-mcpu=cortex-a53 -march=armv8-a".
• we can easily fix this by editing the compile_commands.json to replace "cc" and "c++" with the original cross-compiler name (e.g. "aarch64-ca53v2-linux-gnueabi-gcc" or "aarch64-ca53v2-linux-gnueabi-g++").
• while it is possible for us to work around the issue by post-processing the compile_commands.json file, it would simplify things quite a bit if "bear" could preserve the original compiler executable name, rather than replace it with "cc" or "c++".

[tadcoburnsonos]

I just realized I'm not on the latest version of bear - I'm using 2.3.11. I'll see if this issue is addressed in the latest version - apologies if it is.

[tadcoburnsonos]

It appears that 2.4.4 has the feature I'm looking for. Closing.