aboutsummaryrefslogtreecommitdiff
path: root/generate-version.sh (follow)
Commit message (Collapse)AuthorAgeLines
* generate-version: fix regression where a tagged version was parsed wrong1.8.0Daniel Eklöf2021-06-25-4/+5
| | | | | The regexps didn’t work when the “extra” portion of “git describe” was missing.
* generate-version: add a define for “extra” version informationDaniel Eklöf2021-06-13-4/+6
| | | | | This will be set to “rrr-gNNNNNNN” when building from git, and the empty string otherwise.
* csi: secondary DA: do not pretend we're xtermDaniel Eklöf2020-07-24-1/+8
| | | | | | | | | | | Previously, our secondary DA response indicated a) VT420, b) an XTerm version number. Now, we indicate VT220 (which corresponds to the primary DA response), and we report foot's version number as MMmmpp. I.e major, minor and patch versions, using two digits. E.g. 1.4.2 is encoded as 010402
* generate-version: check for .git directory in *src* dirDaniel Eklöf2020-03-06-1/+1
| | | | | | | | | Instead of trying to run `git --rev-parse --is-inside-work-tree`, check if there's a .git directory under the source directory. This should fix an issue where we incorrectly decided we where in a foot git clone when we're just a subdirectory under another repository.
* generate-version: redirect *both* stdout and stderr to /dev/nullDaniel Eklöf2019-11-27-1/+1
|
* generate-version: handle builds that aren't git clonesDaniel Eklöf2019-11-24-1/+1
|
* meson: fix version generation from gitDaniel Eklöf2019-10-19-0/+38
run_command() was only run at configure time, meaning the generated version (that was passed on to the sources via -DFUZZEL_VERSION) became stale. Fix by implementing a shell script that generates a header file, and wrap this in a custom target that is run every time (but the generated file is only updated when the version changes)