Re: [PATCH 1/2] cpukit: Add the git hash to the version if built from git source.

On 07/11/2017 08:49, Chris Johns wrote: >> Why can't we use a Git post-checkout hook (attached)? > > I tend to get a little uneasy when a VC tool is touching code in a project > underneath another operation. It makes auditing more complicated. If you think > the autoconf change is still not suitab

Re: [PATCH 1/2] cpukit: Add the git hash to the version if built from git source.

On 06/11/2017 17:23, Sebastian Huber wrote: > How reliable is this Autoconf stuff? Haha, that is a leading question! I suppose it depends on how you use it or abuse it as we have in our case. > Do I have to re-build everything after each > Git checkout (cpuopts.h is included in nearly every head

Re: [PATCH 1/2] cpukit: Add the git hash to the version if built from git source.

How reliable is this Autoconf stuff? Do I have to re-build everything after each Git checkout (cpuopts.h is included in nearly every header)? Why can't we use a Git post-checkout hook (attached)? -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone

[PATCH 1/2] cpukit: Add the git hash to the version if built from git source.

Update #3217. --- cpukit/aclocal/git-version.m4 | 16 cpukit/aclocal/rtems-top.m4 | 7 --- cpukit/configure.ac | 2 +- 3 files changed, 21 insertions(+), 4 deletions(-) create mode 100644 cpukit/aclocal/git-version.m4 diff --git a/cpukit/aclocal/git-version.m4