[cfe-dev] Macros for revision number and commit hash

[Chris Lattner via cfe-dev]

On Mar 17, 2019, at 12:51 AM, Roman Lebedev <lebedev.ri at gmail.com> wrote:
>> I’m generally +1 on exposing such metadata.  The only downside I see is that a git pull could cause a relink of the entire world (even if otherwise unnecessary) just to update these fields.  I suspect that this is going to be more painful in a monorepo world for people who work downstream of clang (e.g. LLDB developers).
> 
> That will indeed cause relinking at best, or even recompilation at worst.

Why?  Can’t this be stored in a text file that lives next to the clang binary, which is loaded iff the macro is referenced?

-Chris