summaryrefslogtreecommitdiffstats
path: root/VERSION
diff options
context:
space:
mode:
authorThomas Heijligen <thomas.heijligen@secunet.com>2023-02-01 15:52:26 +0100
committerAnastasia Klimchuk <aklm@chromium.org>2023-05-07 08:36:39 +0000
commitc4d89eadfd45c8dbfdfccc500c5cf34e14afea9a (patch)
tree114f664eb09f60a2fe28fc32bf25c1d1eb271302 /VERSION
parent3d5c9a5cea13e4e9acf73a9dbd5b549a3774b0a4 (diff)
downloadflashrom-c4d89eadfd45c8dbfdfccc500c5cf34e14afea9a.tar.gz
flashrom-c4d89eadfd45c8dbfdfccc500c5cf34e14afea9a.tar.bz2
flashrom-c4d89eadfd45c8dbfdfccc500c5cf34e14afea9a.zip
meson make: use VERSION file
To create a distribution package with meson you run `meson dist -C <your_build_dir>` This will collect all git tracked files and pack them into an archive. There is no way to collect version information for that. So now the base version stands in the VERSION file. To relase a flashrom version you change that file and tag the changing commit. When building from git the git version is embedded in the flashrom binary. E.g.: flashrom 1.4.0-devel (git:v1.2-1172-g7f186838) on Linux 6.1.3 (x86_64) Change-Id: Idc17eadb397b3c579bddfbf9ae6bf1b171f5dfb7 Signed-off-by: Thomas Heijligen <thomas.heijligen@secunet.com> Reviewed-on: https://review.coreboot.org/c/flashrom/+/72657 Reviewed-by: Anastasia Klimchuk <aklm@chromium.org> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'VERSION')
-rw-r--r--VERSION1
1 files changed, 1 insertions, 0 deletions
diff --git a/VERSION b/VERSION
new file mode 100644
index 000000000..90e4bc277
--- /dev/null
+++ b/VERSION
@@ -0,0 +1 @@
+1.4.0-devel