quinzee.cloud

Development edition · 16 November 2026. Commands using repository paths, Make targets or sample projects require access to the Quinzee source checkout. No public installer is available. Examples use disposable local environments.

Developer’s guide

17. Build Quinzee from source

You need a native build to modify the C++ emulator or run QHQ. The application quickstart builds its cloud image separately, so it does not require a prior native build.

On Linux x86-64, install GCC/G++ 13 or newer, CMake 3.28 or newer, GNU Make, Bash, Git, curl, tar, Perl, Python 3.9+, sha256sum, flock and binutils. Docker Engine, Compose v2 and BuildKit support the container targets. A graphical QHQ session also needs SDL2. The verified build uses GCC 15.2, CMake 4.2, Boost 1.92.0 and OpenSSL 3.5.9. The repository manifest selects exact dependencies; make deps verifies and builds them instead of linking arbitrary system libraries.

From the repository root:

make deps
make
make test

Builds run in parallel. Boost, OpenSSL and the independent Simple UI toolkit come from verified sources in .packages/. The Simple revision is obtained from GitHub; a nearby ../simple checkout is not used for linking. Existing Git credentials may be needed to fetch its repository. No credentials should be copied into dependency manifests or container images.

Command Output/use
make Debug binaries under bin/debug/
make PRESET=release Hardened release binaries under bin/release/
make qhq QHQ and its assets
make rasta The development viewer under bin/tools/rasta
make test C++ unit/integration/dependency and helper contract tests
make docker-test Disposable container, HTTPS, DNS and SDK checks
make application-check .NET/frontend formatting/build and browser accessibility checks
make docker-lint C++ formatting and static analysis using the container toolchain

For a native service-only build, configure with cmake --preset debug -DTRIGLAV_BUILD_QHQ=OFF, then build with make. Set it back to ON before building QHQ. Do not install unrelated system Boost or OpenSSL versions to bypass the project's pinned dependencies.

make clean removes build/ and bin/ while keeping the dependency cache. make purge is broader and forces downloads/rebuilds; inspect its effects before using it. Neither command is an application data-backup procedure.

For memory checking, build with make PRESET=asan, then run ctest --preset asan --output-on-failure. For race checking use the tsan preset. If the sanitizer cannot start because the environment blocks its address-space requirements, report the run as incomplete. Do not weaken security settings to turn that startup failure into a claimed pass.

PostgreSQL client source builds also require Bison, Flex and bzip2. The Docker builder installs these tools; native builds need them on PATH.