The Nexus ecosystem
Nexus is a development ecosystem spanning native programming, an integrated development environment, structured models, build and workflow automation, and mobile and game development. Six principal products connect these activities while keeping their responsibilities clear.
The product family
| Product | Responsibility | Guide |
|---|---|---|
| Nexus Pascal | Object Pascal compiler, destination runtimes, and compiler-native runtime packages | Compiler and runtime |
| Nexus Build | Project build system for Pascal, C, and C++, with dependency planning and published resources | Project builds |
| Nexus Script | Structured modeling language with references, composition, targets, dialects, and model output | Language guide |
| Nexus Forge | Workflow automation around builds, downloads, files, generated artifacts, and assembly | Workflow automation |
| Nexus Code | Integrated development environment built on VS Code, with language services, projects, builds, and native debugging | Development environment |
| Nexus Gear | Mobile application and game development on a shared Lua-powered engine, including desktop games | Application controls and native plugins |
How the products connect
Nexus Code brings Pascal and Nexus Script language services, project context, build targets, and native debugging into the workspace. VS Code provides the underlying editor platform. Nexus Pascal supplies compilation and runtimes; Nexus Script describes projects and their relationships. Nexus Build executes the dependency graph, and Nexus Forge composes builds with wider automation.
C and C++ dependencies can participate in the same graph as Pascal applications. Native producers publish their resource directories; Pascal applications link compatible objects and libraries through explicit declarations and bindings. See native project integration for examples and the current interoperability boundaries.
Nexus Gear connects mobile application and game development through shared concerns: lifecycles, rendering, input, multimedia, assets, and platform behavior. Its Lua application controls support business applications as well as games. Pascal plugins use the native bridge and matching libraries; they do not require rewriting the engine in Pascal or make every Gear application depend on a plugin.
The products can also be used independently. Command-line development does not require VS Code. Gear's Lua authoring and debugging use their own tooling; Nexus Code's Pascal and Nexus Script services support the corresponding parts of the workflow. Consult platform support for the distinction between build configurations and validated application destinations.
Supporting tools and libraries
| Component | Responsibility |
|---|---|
| Nexus Setup | Installation of prebuilt products and selected development dependencies |
| NexusLS / NexusScriptLS | Separate Pascal and Nexus Script analysis services |
| Desktop GUI libraries | Pascal controls for conventional desktop application interfaces |
| NexusTest | Test suites, runners, and loadable-module protocol |
The Nexus libraries provide reusable components alongside the product family. Technical command names, setting IDs, descriptor names, and repository paths remain distinct from public product names.
Source repositories
- nexus: Nexus Build, Nexus Script, Nexus Forge, Nexus Code, Setup, and product recipes.
- nexus-fpc: Nexus Pascal compiler, RTL, and compiler build recipes.
- nexus-mobile: Nexus Gear engine, platform implementations, and embedded Lua controls.
- nexus-lab: examples and experimental applications.
- Package repositories under
nexus/packages/: shared owned, external, and Apple packages.
Keep source-checkout layout separate from an installed release. An end-user project should use its installed tools and declared dependencies, not a maintainer's personal worktree paths.
See system boundaries for implementation ownership and source builds for repository setup.