Vix.cpp v2.3.1

Vix.cpp v2.3.1 is a patch release focused on packaging and cross-platform stability. This release improves how VixConfig.cmake resolves OpenSSL for consumer projects, especially on macOS environments where OpenSSL is installed through Homebrew and may not be available on the default CMake search paths.

OpenSSL package resolution

The main fix in this release is better OpenSSL resolution in VixConfig.cmake. Consumer projects should be able to import and use Vix without manually fighting CMake package discovery when OpenSSL is installed in a non-default location. This is especially common on macOS, where Homebrew installs OpenSSL outside the default system paths. Vix.cpp v2.3.1 improves that behavior so downstream projects can configure more reliably.

Consumer project stability

This release avoids build failures caused by OpenSSL being installed but not discoverable through the default CMake search paths. That matters because package configuration should be reliable for users consuming Vix as an installed SDK. A runtime library is not only judged by its internal code. It must also be easy to import, configure, and link correctly from external projects.

Highlights

  • Improved OpenSSL resolution in VixConfig.cmake.
  • Improved consumer project compatibility on macOS.
  • Improved support for Homebrew-based OpenSSL installations.
  • Avoided build failures when OpenSSL is installed outside default CMake search paths.
  • Improved installed package stability for downstream Vix users.

Compatibility

Vix.cpp v2.3.1 introduces no breaking changes.

There are no changes to vix run behavior. There are no runtime feature changes in this release. Existing projects should continue to work normally, with improved package configuration behavior when OpenSSL is required.

Notes

Vix.cpp v2.3.1 is intentionally small. It focuses on one important packaging problem: making installed Vix projects more reliable for consumers, especially on systems where OpenSSL is not located in a standard CMake search path. This kind of patch release is important for a C++ runtime ecosystem because reliable package discovery is part of the developer experience.