Manually specify git commit hash
authorAnton Gladky <gladk@debian.org>
Thu, 12 May 2022 21:48:46 +0000 (16:48 -0500)
committerRyan Pavlik <ryan@ryanpavlik.com>
Wed, 7 Dec 2022 22:25:41 +0000 (22:25 +0000)
Revise on every upstream update!

Forwarded: not-needed
Last-Update: 2022-06-30
===================================================================

Gbp-Pq: Name 01_hardcode_git_hash.patch

CMakeLists.txt

index 399e2cae2e48626c44a80d04916ef1644cebb7ae..8451dead5a91ee47aedbc932f44a16d5d4d51877 100644 (file)
@@ -34,9 +34,9 @@ endif()
 # NOTE TO PACKAGERS: The embedded git commit hash is critical for rapid bug triage when the builds
 # can come from a variety of sources. If you are mirroring the sources or otherwise build when
 # the .git directory is not present, please comment the following line:
-include(GetGitCommitHash)
+include(GetGitCommitHash)
 # and instead uncomment the following, adding the complete git hash of the checkout you are using:
-# set(GIT_COMMIT_HASH 0000000000000000000000000000000000000000)
+set(GIT_COMMIT_HASH 70bde63cb32a7f049fa56cbdf924e2695fcb2916)
 
 string(SUBSTRING "${GIT_COMMIT_HASH}" 0 8 solvespace_GIT_HASH)
 project(solvespace