• LLVM/Clang 17+ — C compiler (clang-cl.exe, the MSVC-compatible Clang driver)
• Visual Studio 2019+ (or Build Tools for Visual Studio) — provides Windows SDK, rc.exe, and link.exe
• CMake 3.16+
• Ninja build system
• Git
• Qt Creator (optional, as IDE)

Open a Developer Command Prompt for VS, then:

git clone https://github.com/KaiUR/CatiaMenuWin32
cd CatiaMenuWin32
cmake -S . -B build -G "Ninja" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER=clang-cl
cmake --build build

The executable is output to build/CatiaMenuWin32.exe.

1. Open CMakeLists.txt in Qt Creator
2. Select a Clang kit configured with the MSVC toolchain
3. Add -DCMAKE_C_COMPILER=clang-cl to the CMake arguments
4. Build → Build All

Tip: Launch Qt Creator from a Developer Command Prompt for VS so that rc.exe and the Windows SDK are on the PATH.

The workflow (.github/workflows/release.yml) runs on windows-latest using:

• ilammy/msvc-dev-cmd — sets up the MSVC environment (Windows SDK, rc.exe, link.exe)
• LLVM/Clang (pre-installed on windows-latest) as the C compiler
• Ninja as the build backend

On a tagged release (v*) the workflow additionally:

1. Builds with -DCMAKE_C_COMPILER=clang-cl -DVERSION_OVERRIDE=<version>
2. Authenticode-signs CatiaMenuWin32.exe via PowerShell + signtool.exe (x64)
3. Commits the incremented build_number.txt back to main as a verified bot commit
4. Imports the GPG key, deletes the base tag, creates a GPG-signed tag with the full build number (e.g. v1.2.0.31), and publishes the GitHub Release

The following secrets must be set in Settings → Secrets → Actions:

The following secrets are used by crazy-max/ghaction-import-gpg@v6 to sign release tags:

The imported key is configured as the git signing key; every release tag is created with git tag -s, producing a verified tag on GitHub. The committer identity baked into the key must match KaiUR / kairathjen@yahoo.com as set in the workflow.

src/ C source and header files
res/ Resource files (icons, manifest, resource.rc.in, version.h.in)
docs/ GitHub Pages documentation
.github/ GitHub Actions workflows and issue templates

• Version is determined from the latest Git tag at CMake configure time
• build_number.txt increments by 1 on every CMake configure (local and CI)
• Local builds show a (local) suffix and skip the update check
• CI workflow: tag push → build → sign → release → commit build_number.txt back to main

1. Develop on develop branch
2. Open a pull request to main
3. Merge the PR
4. Tag from main: git tag v1.x.x && git push origin v1.x.x
5. GitHub Actions builds, signs, and creates the release automatically

• C11, Win32 API only — no external libraries

• Unicode throughout — WCHAR, L"" literals, _snwprintf_s

• Memory-safe functions only — always use _s (C11 Annex K) or bounded variants; never use functions flagged by clang-analyzer-security.insecureAPI:

  Never use	Use instead	Notes
  strcpy, wcscpy	strcpy_s, wcscpy_s	always pass _countof(dest)
  strcat, wcscat	strcat_s, wcscat_s	always pass _countof(dest)
  strncpy, wcsncpy	strncpy_s, wcsncpy_s	_s variant guarantees NUL termination
  sprintf, swprintf	sprintf_s, swprintf_s	pass _countof(buf)
  snprintf, _snwprintf	_snprintf_s, _snwprintf_s	use _TRUNCATE as the count argument
  fprintf	fprintf_s
  vsprintf, vswprintf	vsprintf_s, vswprintf_s
  gets	fgets
  memcpy	memcpy_s	pass destSize then count
  memmove	memmove_s	pass destSize then count
  memset (zeroing secrets)	SecureZeroMemory	prevents compiler from eliding the zero

• All GDI painting double-buffered

• All state in global AppState g struct

• Heap memory for scripts — use Folder_Alloc / Folder_Free / Folder_Push helpers; always free on every exit path

• Use COL_BG(), COL_TEXT() etc. — never hardcode RGB values

• Cross-thread communication via PostMessage only