Never Asked Questions

Why Nexus?

Nexus brings the compiler, project description, automation, editor services, and application libraries into one development system. The goal is explicit, repeatable native application development with Object Pascal and useful supporting languages.

Must I use VS Code?

No. Nexus Build, Nexus Forge, Nexus Pascal, and Nexus Script have command-line entry points. VS Code adds project selection, language services, and debugging.

Must I install Lazarus or upstream FPC?

Not for ordinary Nexus Pascal application development from a prebuilt Nexus release. Existing FPC/Lazarus adapters are available for projects that select those tools.

Building Nexus Pascal from source has a separate seed requirement: stock FPC 3.2.2. After bootstrapping, Nexus product builds use Nexus Pascal.

Why both Nexus Build and Nexus Forge?

Nexus Build builds a project and its dependency graph. Nexus Forge composes builds with other work such as downloads, copying, rendering, and packaging. Nexus Forge's NXBuild task uses the same project engine as standalone Nexus Build.

Why Nexus Script?

The tools need to express reusable definitions, relationships, and target variants. Nexus Script provides those mechanisms once; tool-specific dialects describe which data each consumer accepts.

Can I build business applications?

Yes. The desktop GUI libraries serve desktop interfaces. The mobile engine's Lua controls provide panels, edits, labels, lists, and touch-oriented controls for phone applications as well as games. These are distinct interface priorities.

Is Nexus Pascal binary-compatible with upstream FPC?

Its compiled-unit and package identities are distinct. Use matching Nexus Pascal compiler/RTL/SDK artifacts and rebuild dependencies when their compatibility contract changes.

What about licensing?

Components retain their own licenses and notices. Start with Licenses and the centralized attribution record.