Set up your development den.

01 / Verify your tools

The root CMakeLists.txt declares project(noqeri VERSION 0.1.4), CMake 3.16 minimum and C++17. Install Git, CMake and a compatible C++ compiler. Full optional builds may need extra system libraries; the compiler target is the shortest start.

git clone https://github.com/EMN90909/Noqeri.git
cd Noqeri
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release
cmake --build build --target noqeri --parallel 2

02 / Identify the executable

The standard single-config build writes build/noqeri on Linux and typically build/noqeri.exe on Windows. Multi-config environments may place the program under build/Release. Output paths vary by generator.

./build/noqeri --version
./build/noqeri check examples/hello.noqeri
./build/noqeri run examples/hello.noqeri

03 / Build the native web tool separately

The Noqeri native web compiler is a distinct C++17 executable. Static pages and the supported build-client subset are compiled without Node.js. Do not confuse this with the experimental Node-hosted browser-view builder.

cmake --build build --target noqeri-web --parallel 2
./build/noqeri-web build examples/native_web_static dist/site
./build/noqeri-web build-client examples/native_web_client dist/browser

04 / Know what the build proves

Stage-0 can check, interpret, produce NIR, freestanding x86-64 assembly and NQRI bytecode. The build command does not automatically create a Linux or Windows executable. Separate assembler, linker, ABI and platform adapter contracts apply.

05 / Confirm the release evidence

The repository reports a 0.1.4 developer preview, not a blanket production-ready release. Check the release feed and exact architecture, checksum, build artifacts and qualification logs before redistribution.