Build the stack we build with.
Living engineering documentation for the native technologies behind Genyleap: modern C++, Boost, Qt, CMake, LLVM and WebAssembly across desktop, mobile and browser targets.
Current Genyleap engineering profile
Modern C++
C++26-first architecture, project modules, std::expected, std::println, CMake, Ninja, diagnostics and cross-platform toolchains.
Native librariesBoost
Current Boost source builds, architecture-specific binaries and modern CMake integration for the Genyleap native stack.
Application frameworkQt
Current stable Qt source builds and target setup for desktop, Android, iOS and WebAssembly, with version data refreshed from official sources.
One engineering model, every target.
Platform-specific details are isolated at the toolchain boundary. The application and domain architecture stay portable while compilers, SDKs, packaging and deployment remain explicit per target.
Version data is not baked into the prose.
External toolchain versions move. The Stack Development Guide resolves the current stable Boost and Qt releases, Qt Creator release and Qt compatibility data from official upstream sources into one cached manifest, then renders every platform guide from that single source of truth.
Resolve
Official Boost and Qt release indexes plus current platform documentation are checked automatically.
Cache
A local manifest keeps documentation fast and stable even if an upstream endpoint is temporarily unavailable.
Render
Paths, source archive names, NDK/JDK requirements, Emscripten and IDE versions are generated from the current manifest.
Engineering reference, not a beginner tutorial.
Project-owned C++ modules, explicit ownership, RAII, concepts, expected-based errors and current standard-library facilities.
Separate build trees, explicit compiler selection, target-specific SDKs and verified command-line builds before IDE setup.
OS-specific behavior and third-party adaptation stay isolated instead of leaking into domain code.
Configure, build, lint, test and smoke-check the requested product surface before calling an environment ready.
Engineering authority.
The C++ examples and project shape follow the Genyleap modern C++ engineering contract, while changing external version facts are resolved from upstream documentation.