Vix.cpp v2.1.11

Vix.cpp v2.1.11 is a major SDK packaging release. This release introduces full SDK distribution across Linux, macOS, and Windows. Instead of shipping only CLI binaries, Vix now produces complete installable SDK artifacts with a standard layout containing bin, include, and lib. The focus of this release is integration. Vix should not only be executable as a command-line tool. It should also be installable as a C++ SDK that other projects can consume.

Full SDK packaging

Vix.cpp v2.1.11 introduces a dedicated SDK release workflow. The new SDK packaging system produces complete installable artifacts for the major supported platforms:

vix-sdk-linux-x86_64.tar.gz
vix-sdk-macos-aarch64.tar.gz
vix-sdk-windows-x86_64.zip

These artifacts are designed for real C++ integration workflows, not only CLI usage. A proper SDK needs headers, libraries, and binaries in a predictable layout. This release establishes that distribution model.

Installable SDK layout

SDK artifacts now contain the full installation layout:

bin/
include/
lib/

This is an important shift from CLI-only releases. The bin directory provides executable tools such as the vix CLI. The include directory provides public headers for C++ consumers. The lib directory provides compiled libraries and package metadata needed for linking. This layout makes Vix more usable as a native C++ dependency in external projects.

Windows SDK packaging

This release fixes Windows SDK packaging. The Windows workflow now performs a proper build, install, and zip packaging process using vcpkg and the CMake toolchain. That matters because Windows packaging often has different dependency and toolchain behavior from Linux and macOS. Vix.cpp v2.1.11 brings Windows closer to the same SDK distribution model used on the other platforms.

Cross-platform build consistency

The SDK build environments for Linux, macOS, and Windows were aligned to produce consistent SDK layouts. This improves predictability for users and maintainers. A developer should not need to learn a different package structure for each operating system. The platform-specific archive format may differ, but the internal SDK layout should remain consistent.

Release workflow separation

Vix.cpp v2.1.11 separates CLI releases from SDK releases. The release architecture now distinguishes between:

release.yml
sdk-release.yml

release.yml remains focused on CLI release artifacts. sdk-release.yml is dedicated to SDK packaging. This separation makes the release process clearer and easier to maintain. CLI distribution and SDK distribution have different goals, so they should not be forced into the same workflow.

Real-world integration path

This release prepares Vix for real-world integration workflows. A C++ runtime ecosystem needs an SDK distribution model so external projects can install Vix, include its headers, link its libraries, and use its tooling without depending on the source repository layout. Vix.cpp v2.1.11 establishes that foundation.

Highlights

  • Added full SDK packaging across platforms.
  • Added a dedicated SDK release workflow.
  • Added installable SDK artifacts for Linux.
  • Added installable SDK artifacts for macOS.
  • Added installable SDK artifacts for Windows.
  • Added SDK archives: vix-sdk-linux-x86_64.tar.gz, vix-sdk-macos-aarch64.tar.gz, and vix-sdk-windows-x86_64.zip.
  • Added full SDK layout with bin, include, and lib.
  • Fixed Windows SDK packaging.
  • Added proper Windows build, install, and zip packaging.
  • Integrated vcpkg and CMake toolchain usage for Windows SDK builds.
  • Aligned dependency installation across Linux, macOS, and Windows SDK workflows.
  • Separated CLI release workflow from SDK release workflow.
  • Prepared Vix for external C++ integration workflows.

Compatibility

Vix.cpp v2.1.11 introduces no breaking changes. Existing CLI releases remain supported. The main difference is that Vix now has a separate SDK distribution path in addition to CLI releases. Developers who only need the vix command can continue using CLI artifacts. Developers who want to integrate Vix into C++ projects can use the SDK artifacts.

Notes

Vix.cpp v2.1.10 stabilized builds across platforms. Vix.cpp v2.1.11 introduces the complete SDK distribution model. This release is important because it moves Vix beyond a CLI-centered release process and prepares it for real C++ adoption as an installable runtime SDK.