Configure the editor

Nexus has separate settings for build tools and editor behavior.

Build tools

Setup writes nexusPascal.nxbuildPath when that setting is absent. It points to the installed Nexus Build executable. Without it, the default command is nxbuild, resolved through PATH.

Compiler, LLVM, MSVC, and SDK settings live in the adjacent NXBuild.Environment.nxscript. Projects select them explicitly. See Tool environment.

An absolute Nexus Build path also identifies the installation for the editor: the extension can use that installation's language servers and dialect files. A bare command works for launching builds but does not identify an installation directory for editor configuration; the bundled servers/dialects remain available.

Build and analysis targets

Use Nexus: Select Build and Analysis Targets, or edit workspace settings:

{
  "nexusPascal.targets": [
    {"kind": "TargetOS", "value": "win64"},
    {"kind": "TargetCPU", "value": "x86_64"},
    {"kind": "BuildConfiguration", "value": "Debug"}
  ]
}

Use linux on Ubuntu. Additional target kinds are allowed. These are explicit selections, shared by generated build tasks and Nexus Script analysis. HostOS and HostCPU describe the machine running the tools.

Pascal toolchain context

The Pascal toolchain configuration UI supplies source-analysis context and supports existing FPC/Lazarus project adapters. It is distinct from Nexus Build's environment file. Changing an editor-only toolchain setting does not rewrite a Nexus Build recipe.

Keep the selected project, compiler/source paths, and intended target consistent. The settings reference identifies the main configuration surfaces.