oxen-core/src/version.cpp.in

#include "version.h"

const std::array<uint16_t, 3> LOKI_VERSION = {@PROJECT_VERSION_MAJOR@, @PROJECT_VERSION_MINOR@, @PROJECT_VERSION_PATCH@};

const char* const LOKI_VERSION_TAG = "@VERSIONTAG@";
const char* const LOKI_VERSION_STR = "@PROJECT_VERSION@";
const char* const LOKI_RELEASE_NAME = "@LOKI_RELEASE_CODENAME@";
const char* const LOKI_VERSION_FULL = "@PROJECT_VERSION@-@VERSIONTAG@@LOKI_RELEASE_SUFFIX@";
version: fix link to new version strings p2p uses it, and the cpp file needs to know the symbols should be public 2017-09-25 20:01:56 +02:00			`#include "version.h"`

Move version into top-level CMakeLists.txt CMake already provides variables to handle the version major/minor/patch if we give it the dotted version in the `project()` command. Using it significantly reduces the amount of macro stuff we have to do in version.cpp.in, and it seems a little nicer to have it defined in the project top level rather than buried in a needs-to-beprocessed .cpp file. This moves the release codename there, too, so that it stays being defined in essentially the same place as the version. This change here requires some minor tweaking of the version generation code to do it in two steps (when we have git): the first (`src/version.cpp.in` -> `build/version.cpp.in`) replaces all the main version variables during cmake configuration, the second (`build/version.cpp.in` -> `build/version.cpp`) then replaces the VERSIONTAG at build time. (Before this commit, there was only version tag replacement that only happened at build time). Also bumps up the version here (since I'm moving it anyway) to match master's 7.1.8. 2020-05-03 20:45:26 +02:00			`const std::array<uint16_t, 3> LOKI_VERSION = {@PROJECT_VERSION_MAJOR@, @PROJECT_VERSION_MINOR@, @PROJECT_VERSION_PATCH@};`
Add versioning to uptime proofs to enforce behaviour 2018-11-05 05:38:24 +01:00
Move version into top-level CMakeLists.txt CMake already provides variables to handle the version major/minor/patch if we give it the dotted version in the `project()` command. Using it significantly reduces the amount of macro stuff we have to do in version.cpp.in, and it seems a little nicer to have it defined in the project top level rather than buried in a needs-to-beprocessed .cpp file. This moves the release codename there, too, so that it stays being defined in essentially the same place as the version. This change here requires some minor tweaking of the version generation code to do it in two steps (when we have git): the first (`src/version.cpp.in` -> `build/version.cpp.in`) replaces all the main version variables during cmake configuration, the second (`build/version.cpp.in` -> `build/version.cpp`) then replaces the VERSIONTAG at build time. (Before this commit, there was only version tag replacement that only happened at build time). Also bumps up the version here (since I'm moving it anyway) to match master's 7.1.8. 2020-05-03 20:45:26 +02:00			`const char* const LOKI_VERSION_TAG = "@VERSIONTAG@";`
			`const char* const LOKI_VERSION_STR = "@PROJECT_VERSION@";`
			`const char* const LOKI_RELEASE_NAME = "@LOKI_RELEASE_CODENAME@";`
Add a LOKI_RELEASE_SUFFIX for adding "-dev" to dev branch builds This will require a one-time change when we merge to master (to delete the `-dev`) but after that it should just sit there without needing any modifications on `master` or `dev`. (And letting it be specified via cmake arguments will let me slightly simplify the debs which currently have to add a vaguely similar patch to get the debian version into the version string). 2020-05-04 03:10:09 +02:00			`const char* const LOKI_VERSION_FULL = "@PROJECT_VERSION@-@VERSIONTAG@@LOKI_RELEASE_SUFFIX@";`