Forum
    • Categories
    • Register
    • Login

    HISE develop build does not show Git commit hash after building specific commit (VS2022)

    Scheduled Pinned Locked Moved General Questions
    6 Posts 2 Posters 45 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      the red_1
      last edited by

      Hello everyone,

      I’m facing a confusing issue with HISE develop build and I hope someone can clarify it.
      I cloned HISE from GitHub at this specific commit:

      3c36e36c0c27adf97be22206fdebf87ec9c7eeb0
      

      Then I built the standalone app successfully using Visual Studio 2022 (x64, Release).
      The generated executable is located here:

      D:\HISE-3c36e36c0c27adf97be22206fdebf87ec9c7eeb0\projects\standalone\Builds\VisualStudio2022\x64\Release\App\HISE.exe
      

      The build finishes without errors, and HISE.exe runs normally.

      However, when I open Help → About HISE, I see:

      Version: 4.1.0

      Git commit hash: “current hash…” (not showing the actual commit)

      Clicking Show commit on GitHub does not point to my commit

      So it looks like the executable was built correctly, but it does not embed or display the Git commit hash, even though I built directly from a specific commit.

      My questions:
      Is this expected behavior when building HISE from source?
      Is there an extra step required to embed the Git commit hash into the build?
      Could this be related to building outside a Git environment or missing Git metadata during build?
      Is the executable actually using the correct commit internally, even if it doesn’t show it in “About HISE”?

      I’ve attached screenshots of:
      Capture d'écran 2025-12-22 004119.png Capture d'écran 2025-12-22 004143.png
      The About HISE window

      The Release\App folder containing HISE.exe

      Any clarification would be greatly appreciated.
      Thanks in advance 🙏

      David HealeyD T 3 Replies Last reply Reply Quote 0
      • David HealeyD
        David Healey @the red_1
        last edited by

        @the-red_1 in the source folder run git log and tell me what commit it shows at the top

        Free HISE Bootcamp Full Course for beginners.
        YouTube Channel - Public HISE tutorials
        My Patreon - HISE tutorials

        1 Reply Last reply Reply Quote 0
        • T
          the red_1 @the red_1
          last edited by

          @the-red_1 I ran git log -1 in the source folder and got:

          fatal: not a git repository (or any of the parent directories): .gitCapture d'écran 2025-12-22 192643.png

          1 Reply Last reply Reply Quote 0
          • T
            the red_1 @the red_1
            last edited by

            @the-red_1 5d1403bf-297c-4887-9d08-3519f8df4711-image.png

            I rebuilt HISE after properly cloning the repository using:

            git clone https://github.com/christophhart/HISE.git
            cd HISE
            git checkout 3c36e36c0c27adf97be22206fdebf87ec9c7eeb0

            After rebuilding, the commit hash (short form: 3c36e36c) does appear in the About HISE window,
            as shown in the screenshot, but it disappears shortly after.

            So the commit hash is detected initially, then it vanishes from the About window.
            0349c2b0-a78f-407a-8712-5c35449ac86d-image.png

            David HealeyD 1 Reply Last reply Reply Quote 0
            • David HealeyD
              David Healey @the red_1
              last edited by

              @the-red_1 said in HISE develop build does not show Git commit hash after building specific commit (VS2022):

              git checkout 3c36e36c0c27adf97be22206fdebf87ec9c7eeb0

              Why not build the latest commit? git checkout develop?

              Free HISE Bootcamp Full Course for beginners.
              YouTube Channel - Public HISE tutorials
              My Patreon - HISE tutorials

              T 1 Reply Last reply Reply Quote 0
              • T
                the red_1 @David Healey
                last edited by the red_1

                @David-Healey I thought they were the same thing, I’ll give it a try.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post

                26

                Online

                2.1k

                Users

                13.1k

                Topics

                113.5k

                Posts