Fix cross-platform CMake workflow configuration in GitHub Actions matrix

[Copilot]

The build matrix was failing across macOS, Linux, and Windows due to inconsistent toolchain/bootstrap setup and invalid platform-specific dependency installation. This change aligns CI configuration with the project’s vcpkg-based dependency model and ensures each runner can configure CMake successfully.

• Workflow: normalize dependency/toolchain setup by platform

  • Switched Windows environment initialization to ilammy/msvc-dev-cmd@v1 so cl.exe is available during CMake configure.
  • Added vcpkg bootstrap + cache for Linux/macOS (previously only configured on Windows).
  • Exported VCPKG_ROOT and PATH consistently for non-Windows runners.

• Workflow: remove brittle package-manager assumptions

  • Removed invalid Homebrew dependency (stb) from macOS install step.
  • Reduced Linux apt installs to system-level essentials (ninja-build, libvulkan-dev, glslang-tools), letting vcpkg resolve project libraries.

• CMake presets: make non-Windows builds use vcpkg toolchain

  • Added CMAKE_TOOLCHAIN_FILE=$env{VCPKG_ROOT}/scripts/buildsystems/vcpkg.cmake to linux-base and macos-base presets.

# .github/workflows/main.yml
- name: Setup MSVC Dev Cmd (Windows)
  if: runner.os == 'Windows'
  uses: ilammy/msvc-dev-cmd@v1

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[PR3C14D0]

@copilot CI Builds failing on ubuntu and macOS, Windows untested

[Copilot]

@copilot CI Builds failing on ubuntu and macOS, Windows untested

Addressed in 364a7e5. I updated the workflow to detect the vcpkg manifest path (root or Engine), explicitly install manifest dependencies on all OSes before configure, and set VULKAN_SDK on macOS from molten-vk so FindVulkan resolves correctly.