Windows SDK installation

Download the SDK archive, the Zebvix executable, the PowerShell bootstrap, and the release manifest from the local download page. Save the four files together. This Windows x64 preview is unsigned. Use artifacts from a trusted handoff.

Verify the downloaded files

Open PowerShell in the download directory and compare the hashes with the manifest. Keep the manifest from the same trusted handoff.

$manifest = Get-Content -Raw ./v0.5.0-preview.5.json | ConvertFrom-Json
foreach ($item in @($manifest.bootstrap, $manifest.bootstrapInstaller, $manifest.releases[0])) {
    $file = Get-Item -LiteralPath $item.filename
    $sha = (Get-FileHash -LiteralPath $file.FullName -Algorithm SHA256).Hash
    if ($file.Length -ne $item.size -or $sha -ne $item.sha256) {
        throw "Integrity check failed for $($item.filename)"
    }
}

Install or update

The matching preview.5 bootstrap installs Zebvix in the Windows user profile and configures PATH. Use the matching manifest and executable when starting it.

./zebvix-bootstrap-0.5.0-preview.5.ps1 -Manifest ./v0.5.0-preview.5.json -Artifact ./zebvix-cli-0.5.0-preview.5-windows-x64.exe
zebvix install --version 0.5.0-preview.5 --manifest ./v0.5.0-preview.5.json --artifact ./zbl-sdk-0.5.0-preview.5-windows-x64.tar.gz
zebvix --version
zebvix doctor

For an existing SDK, use zebvix update with the same version, manifest and archive arguments in place of install. The verified update preserves the previous SDK version and rolls back a failed activation. File associations are opt-in. Native executable builds require a compatible LLVM-MinGW Clang toolchain.

Check the installation

zebvix new hello-zbl
Set-Location hello-zbl
zebvix check
zebvix run --engine interpreter
zebvix run --engine bytecode
zebvix test

Both engines should print Hello ZBL!. If a new terminal cannot find Zebvix, open a fresh PowerShell and run Get-Command zebvix. If a candidate archive fails verification, check its hash and use a fresh trusted copy.

Use zebvix uninstall to remove the active managed SDK. The bootstrap and user projects are preserved. For the separate desktop IDE, see the Studio guide.