subsurface/core/version.cpp

// SPDX-License-Identifier: GPL-2.0
#include "ssrf-version.h"

// let's leave the two redundant functions in case we change our minds on git SHAs
const char *subsurface_git_version()
{
	return CANONICAL_VERSION_STRING_4;
}

const char *subsurface_canonical_version()
{
	return CANONICAL_VERSION_STRING;
}
Add SPDX header to remaining core files Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2017-04-27 20:24:53 +02:00			`// SPDX-License-Identifier: GPL-2.0`
add and use a version.c / version.h pair version.c is now object code which is recompiled each time ssrf-version.h changes, while the interface file version.h remains that same at all times and files which include it will not need to be recompiled. Signed-off-by: Lubomir I. Ivanov <neolit123@gmail.com> Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2015-02-15 20:25:18 +02:00			`#include "ssrf-version.h"`

Complete redesign of Subsurface version numbers - for now all versions start with v6.0 - CICD builds use the monolithic build number as patch level, e.g. v6.0.12345 - local builds use the following algorithm - find the newest commit with a CICD build number that is included in the working tree - count the number of commits in the working tree since that commit - if there are no commits since the last CICD build, the local build version will be v6.0.12345-local - if there are N commits since the last CICD build, it will be v6.0.12345-N-local - test builds in the CICD that don't create artifacts simply use a dummy release in order to not incorrectly increment the build number and also not to waste time and resources by manually checking out the nightly-build repo for each of these builds. Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2024-01-04 20:44:31 -08:00			`// let's leave the two redundant functions in case we change our minds on git SHAs`
general: remove (void) function parameter declarations To my understanding, declaring empty parameter lists using "(void)" is an artifact from the bad old K&R times, when functions were declared without(!) parameters. Which in hindsight was an absolute recipe for disaster. So for backwards compatibility, functions without parameters had to be declared using "(void)" as "()" could also mean "any function". That was 40 years ago. Meanwhile, C++ introduced references, which made it a necessity to declare the function parameters. So "(void)" is redundant and inconsistent in C++ code and just makes no sense. Remove it. Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at> 2024-05-04 18:53:41 +02:00			`const char *subsurface_git_version()`
add and use a version.c / version.h pair version.c is now object code which is recompiled each time ssrf-version.h changes, while the interface file version.h remains that same at all times and files which include it will not need to be recompiled. Signed-off-by: Lubomir I. Ivanov <neolit123@gmail.com> Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2015-02-15 20:25:18 +02:00			`{`
Complete redesign of Subsurface version numbers - for now all versions start with v6.0 - CICD builds use the monolithic build number as patch level, e.g. v6.0.12345 - local builds use the following algorithm - find the newest commit with a CICD build number that is included in the working tree - count the number of commits in the working tree since that commit - if there are no commits since the last CICD build, the local build version will be v6.0.12345-local - if there are N commits since the last CICD build, it will be v6.0.12345-N-local - test builds in the CICD that don't create artifacts simply use a dummy release in order to not incorrectly increment the build number and also not to waste time and resources by manually checking out the nightly-build repo for each of these builds. Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2024-01-04 20:44:31 -08:00			`return CANONICAL_VERSION_STRING_4;`
add and use a version.c / version.h pair version.c is now object code which is recompiled each time ssrf-version.h changes, while the interface file version.h remains that same at all times and files which include it will not need to be recompiled. Signed-off-by: Lubomir I. Ivanov <neolit123@gmail.com> Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2015-02-15 20:25:18 +02:00			`}`

general: remove (void) function parameter declarations To my understanding, declaring empty parameter lists using "(void)" is an artifact from the bad old K&R times, when functions were declared without(!) parameters. Which in hindsight was an absolute recipe for disaster. So for backwards compatibility, functions without parameters had to be declared using "(void)" as "()" could also mean "any function". That was 40 years ago. Meanwhile, C++ introduced references, which made it a necessity to declare the function parameters. So "(void)" is redundant and inconsistent in C++ code and just makes no sense. Remove it. Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at> 2024-05-04 18:53:41 +02:00			`const char *subsurface_canonical_version()`
add and use a version.c / version.h pair version.c is now object code which is recompiled each time ssrf-version.h changes, while the interface file version.h remains that same at all times and files which include it will not need to be recompiled. Signed-off-by: Lubomir I. Ivanov <neolit123@gmail.com> Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2015-02-15 20:25:18 +02:00			`{`
			`return CANONICAL_VERSION_STRING;`
			`}`