Dependencies
Application dependencies
Nexus Build projects declare dependencies through imported project catalogs. Each project publishes its own source, header, object, and library directories. Consumers retain the publisher's path context.
These project dependencies are distinct from compiler-native runtime-package dependencies and from Setup's installed system packages.
Development tools
Nexus Setup manages shared dependencies through WinGet on Windows and APT on Ubuntu. The release declares tested package selections. Android SDK packages are managed by Google's SDK manager.
The adjacent NXBuild.Environment.nxscript records configured tool locations.
Projects select those settings explicitly; merely installing a tool does not
add it to every build.
See Tool environment and Setup.
Source ownership
| Consumer | Shared foundations |
|---|---|
| Nexus Build | Nexus Script model/Live, package-independent build helpers |
| Nexus Forge | Nexus Script, Nexus Build engine, filesystem/process/archive/network support |
| Setup | Nexus Script, GUI, package providers, archive/network support |
| Pascal language server | JSON-RPC/LSP, Nexus Pascal analysis, Nexus Build project context |
| Nexus Script language server | JSON-RPC/LSP and the shared Nexus Script compiler |
| Test host/UI | NexusTest module contract; GUI for the visual runner |
Source recipes declare concrete project requirements. Consult those recipes for the complete dependency closure; a prose overview is not a replacement catalog.
Native SDKs
Compiler backends and RTLs do not contain every destination's native SDK. Cross-linking needs matching platform libraries and headers. Windows-to-Linux compiler construction additionally requires an explicitly configured Linux sysroot; the build does not download or infer one.
Original dependency licenses and notices remain with their material. See Attribution.