Vix.cpp v2.1.10

Vix.cpp v2.1.10 is a cross-platform build stability release. This release fixes Windows build failures caused by missing spdlog and fmt, improves dependency consistency across Linux, macOS, and Windows, ensures fmt is linked correctly for logging utilities, and removes unnecessary Boost dependencies. The focus of this release is build reliability. A runtime ecosystem must build consistently across supported platforms before higher-level tooling can be trusted.

Windows dependency resolution

The main fix in Vix.cpp v2.1.10 is resolving Windows build failures caused by missing spdlog and fmt. These dependencies are now included in the vcpkg manifest so Windows builds can resolve them correctly through the standard dependency path. This matters because Windows builds often fail when dependencies are assumed to exist globally or are handled differently from Unix-based systems. Vix.cpp v2.1.10 makes the Windows dependency path explicit.

fmt and logging utilities

This release also ensures that fmt is correctly available as a direct dependency for logging utilities. That is important because logging is used across many runtime and CLI components. If fmt is only available indirectly, builds can become fragile depending on module order, platform behavior, or package manager configuration. Vix.cpp v2.1.10 makes the dependency relationship clearer.

Cross-platform dependency consistency

Dependency setup is now more consistent across the main supported platforms. Linux uses apt. macOS uses brew. Windows uses vcpkg. The goal is not to make every platform identical internally. The goal is to ensure each platform has a clear and reliable dependency installation path. This release reduces platform-specific failures caused by missing or inconsistent dependency setup.

Build reliability

Vix.cpp v2.1.10 eliminates several build issues caused by dependency mismatch between platforms. This improves confidence in release builds, CI builds, and local developer builds. For a C++ project, cross-platform stability depends on more than source code portability. It also depends on reliable dependency declaration, package discovery, linking behavior, and CI environment setup.

Boost dependency cleanup

This release removes unnecessary Boost dependencies, including boost-system and boost-beast. That simplification keeps the project dependency graph smaller and better aligned with the V2 direction of Vix.cpp. Removing unnecessary dependencies also reduces packaging complexity and lowers the risk of platform-specific build failures.

Highlights

  • Fixed Windows build failure caused by missing spdlog and fmt.
  • Added spdlog and fmt to the vcpkg manifest.
  • Ensured fmt is available as a direct dependency for logging utilities.
  • Improved dependency consistency across Linux, macOS, and Windows.
  • Unified platform dependency setup around apt, brew, and vcpkg.
  • Improved build reliability across supported platforms.
  • Removed unnecessary boost-system dependency.
  • Removed unnecessary boost-beast dependency.
  • Reduced platform-specific dependency issues.

Compatibility

Vix.cpp v2.1.10 introduces no breaking changes. Existing projects remain compatible. The main difference is that Windows builds should now resolve required logging and formatting dependencies correctly through vcpkg. Linux, macOS, and Windows builds should now behave more consistently.

Notes

Vix.cpp v2.1.9 stabilized CMake and fmt integration, but Windows builds were still missing required dependencies. Vix.cpp v2.1.10 completes that work by fixing the Windows dependency path and aligning dependency setup across Linux, macOS, and Windows. This release is an important step toward stable cross-platform releases for the Vix ecosystem.