Makefile: track version using p-r-project VERSION file

[oI0ck]

JIRA: RTOS-1318

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Chore (refactoring, style fixes, git/CI config, submodule management, no code logic changes)

How Has This Been Tested?

• Already covered by automatic testing.
• New test added: (add PR link here).
• Tested by hand on: (list targets here).

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing linter checks and tests passed.
• My changes generate no new compilation warnings for any of the targets.

Special treatment

• This PR needs additional PRs to work (list the PRs, preferably in merge-order).
• VERSION: track next version tag phoenix-rtos-project#1623
• port_manager: get current RTOS version from p-r-project/VERSION phoenix-rtos-build#278
• I will merge this PR by myself when appropriate.

[gemini-code-assist]

Code Review

This pull request simplifies the versioning logic in the Makefile by replacing complex git description parsing with a short git hash and reading the release version from an external file. Feedback identifies a shell syntax error in the dummy revision string, suggests handling missing version files to prevent build noise, and recommends restoring the 'dirty' tree flag to aid in debugging kernel issues.

[gemini-code-assist]

The escaped quotes in DUMMY_REVISION will cause a shell syntax error when the fallback echo "$(DUMMY_REVISION)" is executed (e.g., echo ""(unknown)"" results in bash: syntax error near unexpected token '('). Additionally, since VERSION is wrapped in escaped quotes in CPPFLAGS (line 23), this would lead to incorrect double-quoting in the C macro definition (e.g., ""(unknown)"") compared to the git-based version which lacks internal quotes.

DUMMY_REVISION := (unknown)

[gemini-code-assist]

Reading ../VERSION directly will produce an error message on stderr if the file is missing (e.g., in standalone builds or non-standard directory structures). It is better to suppress this error and provide a sensible default value to ensure the build output remains clean.

RELEASE := $(shell cat ../VERSION 2>/dev/null || echo "unknown")

[gemini-code-assist]

The change from git describe --dirty to git rev-parse --short HEAD loses the information about whether the build was performed on a dirty git tree. This information is often crucial for debugging kernel issues. Using git describe --always --dirty allows you to keep the dirty flag while still falling back to the hash if no tags are present.

GIT_REVISION := $(shell git describe --always --dirty --abbrev=8 2>/dev/null || echo "$(DUMMY_REVISION)")