Vix.cpp v2.1.15
Vix.cpp v2.1.15 is an SDK installation and runtime portability release. This release fixes relative runtime library resolution for the SDK binary, improves installer behavior when the CLI is already installed at the target location, enhances installer output across Linux, macOS, and Windows, and makes the SDK runtime more self-contained. The focus of this release is installation reliability. A C++ SDK should not only build correctly. It should also install cleanly, locate its runtime libraries, and give users clear feedback during setup.
Relative RPATH for SDK binaries
The main fix in Vix.cpp v2.1.15 is relative RPATH support for the SDK binary.
The vix executable can now locate its shared libraries relative to its install prefix.
On Unix systems, the runtime path uses:
$ORIGIN/../libOn macOS, it uses:
@loader_path/../libThis improves SDK portability because the executable no longer depends on users manually configuring library paths after installation.
Self-contained SDK runtime
This release refactors the CLI so it resolves dependencies relative to its installation prefix. That makes the SDK runtime more self-contained and reduces the need for manual environment configuration. For developers, this is important because an installed CLI should behave predictably after installation. If the binary exists but cannot locate its shared libraries, the installation is effectively broken. Vix.cpp v2.1.15 strengthens that path.
Same-file symlink handling
The installer now handles same-file symlink cases in SDK mode. This prevents the installer from attempting to create a symbolic link when the CLI is already installed at the target location. That small edge case matters because repeated installations should be safe. A user should be able to rerun the installer without hitting avoidable file or symlink errors.
Installer experience
Vix.cpp v2.1.15 improves the installer experience on Linux and macOS. The installer now uses clearer step-based output with styled messages for steps, success states, and warnings. This makes installation feel more professional and easier to follow. Instead of a raw script-like output, users now get a clearer progression of what is happening and whether the installation completed successfully.
Windows installer output
The Windows installer output was also improved. This release adds structured logs and better feedback during installation, including clearer success and warning messages. The goal is to make installation feedback consistent across platforms, while still respecting platform-specific behavior.
Installation summary
The installer now displays a better final summary after completion.
The summary includes:
- final install location
- installed version
- install kind
This gives users immediate confirmation of what was installed and where it was placed.
Cleaner install flow
Internally, the installer logic was simplified and logging was unified across platforms. This reduces duplicated behavior and makes future installer improvements easier to maintain. Installation is part of the product experience. A clean installer flow helps Vix feel more reliable before the user even runs their first project.
Highlights
- Added relative RPATH support for the SDK binary.
- Added
$ORIGIN/../libruntime path support on Unix. - Added
@loader_path/../libruntime path support on macOS. - Fixed SDK binary shared library lookup after installation.
- Fixed same-file symlink handling in SDK mode.
- Improved Linux installer output.
- Improved macOS installer output.
- Improved Windows installer output.
- Added clearer step-based installer logs.
- Added styled success and warning messages.
- Added a better installation summary.
- Displayed final location, version, and install kind after installation.
- Made the SDK runtime more self-contained.
- Simplified installer flow and unified logging across platforms.
Compatibility
Vix.cpp v2.1.15 introduces no breaking changes. Existing SDK installations remain compatible. The main difference is that new SDK installations should locate their runtime libraries more reliably after installation. Repeated installation in SDK mode should also behave more safely when the CLI already exists at the target location.
Notes
Vix.cpp v2.1.15 is a release engineering and installer quality update. It does not introduce new runtime APIs. It focuses on making the installed SDK easier to use, easier to relocate, and easier to trust across Linux, macOS, and Windows. This is an important step for Vix.cpp because the developer experience starts at installation, not at the first command.