Re: [Chicken-hackers] Bumping version no. / build tag in banner

[Felix]

> As an experiment, I pulled out the Chicken version number, build tag and 
> branch name constants into variables in a separately compiled unit (let's 
> call it "version") and added (uses version) to library.scm.  That ensures 
> these items are always updated in the banner even after a minor change or 
> branch switch, whereas currently you have to recompile library.scm to update 
> the version and `make spotless` to update the build tag or branch.  You could 
> even include the current HEAD commit hash in the version number, without 
> being forced to recompile library.scm at each commit.
> 
> This works fine, *except* that in the case you are linking the Chicken 
> runtime .c files together by hand with gcc runtime.c library.c ..., you also 
> have to add version.c because Unit library depends on it.
> 

Is this necessary? library.c already has a dependency on version.scm.

The commit hash is only available when building from a git checkout.
Rebuilding everything from a tarball will have no way recover that
information.


cheers,
felix