Use cmake to generate the src/version.h file

Author: Doy-lee

CMakeLists.txt

@@ -6,6 +6,28 @@ set(CMAKE_POLICY_DEFAULT_CMP0069 NEW)
 
 set(VERBOSE ON)
 
+# Get current commit hash as GIT_COMMIT
+find_package(Git)
+set(GIT_COMMIT "unknown") # Default value for when Git is not found
+if (EXISTS "${CMAKE_SOURCE_DIR}/.git/index" AND GIT_FOUND)
+    execute_process(COMMAND "${GIT_EXECUTABLE}" rev-parse HEAD RESULT_VARIABLE GIT_GET_HASH_RESULT OUTPUT_VARIABLE GIT_COMMIT OUTPUT_STRIP_TRAILING_WHITESPACE)
+    if(GIT_GET_HASH_RESULT)
+        message(STATUS "You are currently on commit ${GIT_COMMIT}")
+    else()
+        message(WARNING "Cannot determine current commit. Make sure that you are building either from a Git working tree or from a source archive.")
+    endif()
+endif()
+
+# Read the package.json file and extract the top-level .version as LIBSESSION_NODEJS_VERSION
+file(READ "${CMAKE_CURRENT_SOURCE_DIR}/package.json" PACKAGE_JSON)
+string(JSON LIBSESSION_NODEJS_VERSION GET "${PACKAGE_JSON}" version)
+
+# Generate src/version.h
+file(WRITE "${CMAKE_CURRENT_SOURCE_DIR}/src/version.h"
+"const char* LIBSESSION_NODEJS_VERSION = \"${LIBSESSION_NODEJS_VERSION}\";
+const char* LIBSESSION_NODEJS_COMMIT = \"${GIT_COMMIT}\";\n"
+)
+
 # Detect the number of processors
 include(ProcessorCount)
 ProcessorCount(N)
@@ -18,7 +40,6 @@ else()
 endif()
 message(STATUS "Number of processors detected: ${N}")
 
-
 add_definitions(-DNAPI_VERSION=8)
 set(CMAKE_CONFIGURATION_TYPES Release)
 

README.md

@@ -20,7 +20,7 @@ git clone --recursive [email protected]:session-foundation/libsession-util-nodejs.g
 ```
 
 Always do your changes in `[FOLDER_NOT_IN_SESSION_DESKTOP]/libsession-util-nodejs`, never in the one under session-desktop's `node_modules` as you might override your local changes.
-Then, you can quickly compile a non-electron build by first running `yarn naughty-patch && yarn update_version` and then `yarn install` from that folder. You should only have to run `yarn naughty-patch && yarn update_version` manually once when you first setup the project. This is a quick incremental build which can check for C++ compilation errors.
+Then, you can quickly compile a non-electron build by first running `yarn naughty-patch` and then `yarn install` from that folder. You should only have to run `yarn naughty-patch` manually once when you first setup the project. This is a quick incremental build which can check for C++ compilation errors.
 Once your changes are ready to be tested in the `session-desktop` you can compile an electron build using this command:
 
 ```

prepare_release.sh

@@ -14,7 +14,6 @@ python -m venv .venv
 . .venv/bin/activate
 pip install git-archive-all
 PACKAGE_VERSION=$(node -p "require('./package.json').version")
-yarn update_version
 echo "PACKAGE_VERSION: $PACKAGE_VERSION"
 echo "Is '$PACKAGE_VERSION' the correct version? If yes, press 'y' to create the release. Press anything else to exit."
 read_char char_read