Proper version reporting #139

New Issue

claunia · 2026-01-29T16:36:15Z

claunia commented

2026-01-29 16:36:15 +00:00

Originally created by @cfsmp3 on GitHub (May 1, 2016).

Originally assigned to: @canihavesomecoffee on GitHub.

Add parameter --version to display the version number and then exit.
The version number should be something like this:

0.80 (github XXXXXX) - compiled DATE, hash YYYYYY
The 0.80 is just the value of VERSION (a #define), nothing special here.
the github version should display whatever we can generate at build time (I don't know what git can provide here so uniquely identify a specific release).
The compilation date
And finally a MD5 hash of the running binary

This will make our life a lot easier when dealing with reports from advanced users.

This seems easy to do for linux (lots of examples around) and not so sure about Windows (build with Visual Studio).

Originally created by @cfsmp3 on GitHub (May 1, 2016). Originally assigned to: @canihavesomecoffee on GitHub. Add parameter --version to display the version number and then exit. The version number should be something like this: 0.80 (github XXXXXX) - compiled DATE, hash YYYYYY The 0.80 is just the value of VERSION (a #define), nothing special here. the github version should display whatever we can generate at build time (I don't know what git can provide here so uniquely identify a specific release). The compilation date And finally a MD5 hash of the running binary This will make our life a lot easier when dealing with reports from advanced users. This seems easy to do for linux (lots of examples around) and not so sure about Windows (build with Visual Studio).

claunia closed this issue

2026-01-29 16:36:15 +00:00

claunia referenced this issue

2026-01-29 16:59:08 +00:00

[PR #208] Case fix teletext #1087

claunia referenced this issue

2026-01-29 17:00:21 +00:00

[PR #368] [MERGED] Fixes #139 - Case fixing in teletext #1213

Sign in to join this conversation.