Vix.cpp v2.6.2: C++ Developer Toolkit Release with Windows SDK Installer Fix
C++ development should not feel fragile from the first install step.
Today, we released Vix.cpp v2.6.2.
This release is focused on stability, packaging, registry workflows, dependency management, and better diagnostics around the commands developers use every day.
Vix.cpp is a modern C++ runtime and developer toolkit. The goal is to make C++ more practical for real projects: build, run, test, install dependencies, publish packages, deploy services, and debug issues with clearer feedback.
Windows SDK installer fix
One important fix in this release is the Windows SDK installer.
A user reported that the PowerShell installer was failing with a Not Found error while trying to download:
vix-sdk-windows-x86_64.zip
The report was correct.
The installer was trying to install the Windows SDK, but the release pipeline was not publishing the Windows SDK archive. It was publishing the Linux SDK asset, but not the Windows one.
This is fixed in v2.6.2.
The Windows SDK archive is now built, packaged, checksummed, signed, and uploaded as part of the release.
So this should now work correctly:
irm https://vixcpp.com/install.ps1 | iex
You can also force the version explicitly:
$env:VIX_VERSION="v2.6.2"
irm https://vixcpp.com/install.ps1 | iex
Better dependency workflows
This release also improves several registry and dependency commands.
vix update now respects version constraints declared in vix.json. It no longer blindly resolves direct dependencies to the latest registry version when a project has already declared constraints.
It also avoids reprocessing every dependency when only some dependencies actually need updates.
vix install now reports only dependencies that were actually installed or relinked. This makes the output much clearer, especially when working with an existing vix.lock.
vix list and vix outdated now show direct project dependencies by default. If you want the full locked dependency graph, you can still use:
vix list --all
and:
vix outdated --all
This makes the default output more useful for normal project maintenance.
Better vix run
vix run now works better with generic CMake projects.
Before, it could assume that the executable name matched the folder or project name. That is not always true.
Now it detects and runs the executable produced by the build, which makes vix run more useful outside of perfectly shaped Vix projects too.
Better diagnostics
v2.6.2 also improves diagnostics in multiple places.
CMake errors with multi-line message(FATAL_ERROR ...) output are now displayed more clearly instead of being collapsed into unreadable one-line messages.
vix tests failure output is now easier to understand. Failed test names, source locations, focused error messages, and compact code frames are summarized better.
vix.app also gives clearer errors when .vix/vix_deps.cmake is missing or when a required resource does not exist.
The goal is simple: when something fails, the tool should help you understand the problem faster.
Registry and package improvements
This release improves transitive registry dependency propagation.
For example, packages like rix/rix can expose dependencies such as:
rix/csv
rix/debug
rix/auth
without forcing every application to list all of them manually.
This is important for the direction of the Vix and Rix ecosystem.
Rix is the official package namespace for optional Vix.cpp libraries in the Vix registry. As more packages are added, dependency propagation needs to feel reliable and predictable.
Crypto helpers
v2.6.2 also adds new crypto helpers:
- constant-time byte comparison helpers
- PBKDF2-HMAC-SHA256 password hashing and verification helpers
These are small but important building blocks for security-sensitive code.
Why this release matters
Not every release needs to be about a big visible feature.
Sometimes the important work is making the normal workflow more reliable:
install
build
run
test
install dependencies
update dependencies
publish packages
deploy
debug
repeat
That is what v2.6.2 is about.
Vix.cpp is still moving toward the same goal: a modern C++ runtime and developer toolkit that is practical for real applications, not just demos.
Links
GitHub repo:
Release:
https://github.com/vixcpp/vix/releases/tag/v2.6.2
Website:
Top comments (0)