THE PROJECT BUILDER

Nexus Build

Make the build explicit.

Nexus Build builds projects described in Nexus Script. It loads the declared dependency graph, builds producers before consumers, and passes published source, header, object, and library directories to dependent projects.

Describe the work

A project can compile an application, build a library, generate an input, or publish existing sources without compiling anything. Tool choices and output locations are part of the description.

One dependency graph. More than one language.

Make C and C++ projects producers in the same graph as your Pascal application. Nexus Build orders their construction and propagates published source, header, object, and library directories to consumers, including through intermediate dependencies.

Use Clang through LLVM, or explicit CMake, MSBuild, and MSVC operations where a library needs its existing native build. A CMake project retains its internal build graph; the Nexus project coordinates that operation and publishes its outputs.

Pascal remains your application language. The NXArchive provider compiles native C codecs for Pascal consumers; Nexus Gear combines C/C++ engine builds with explicit native interfaces for Pascal plugins.

Published directories provide lookup paths. Bindings, object filenames, library names, and linker settings still select the interface and inputs. This does not provide automatic C++ class interoperability or remove platform SDK and runtime requirements.

Build native dependencies with Pascal

Inspect before executing

The command line supports validation, planning, and building. Use the same project description when reviewing the dependency plan and when performing the build.

nxbuild /action=plan /project=Hello.nxproject
nxbuild /action=build /project=Hello.nxproject

Use it with the wider workflow

Nexus Build owns project execution and compiler configuration. Nexus Forge can compose that build with filesystem work, archives, and other automation. Each tool keeps a clear responsibility.

Nexus Build documentation First application

See tool environment configuration and the operation reference.

From the workspace to the application

Nexus Code uses Nexus Build projects and target selections in the IDE. Engine and native plugin construction for Nexus Gear also use explicit build descriptions; platform SDKs and application packaging remain separate responsibilities.