feature: log scuff-em version (from git) to output files.#199
Open
texnokrates wants to merge 6 commits intoHomerReid:masterfrom
Open
feature: log scuff-em version (from git) to output files.#199texnokrates wants to merge 6 commits intoHomerReid:masterfrom
texnokrates wants to merge 6 commits intoHomerReid:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As no software is perfect, it is useful to keep track about which version was used for generating a given output.
This PR introduces some some features in this regard. During build, a string generated by
git describeis passed as a macro to all application sources. This string is then included in the output files, so one can easily check which git version of scuff-em was used. The version string is now also printed by OSUsage().The downside of the approach used here is that it uses the $(shell ...) construct in Makefile.am, which is a GNU extension, so it might affect portability when built with a non-GNU make. And of course, git is also required.