Troubleshooting

A command is not found

After Setup changes PATH, open a new Windows terminal or sign in again on Ubuntu. Check nxbuild /help and nxforge /help. An explicit nexusPascal.nxbuildPath must name the installed executable.

A compiler or SDK path is wrong

Inspect bin/NXBuild.Environment.nxscript beside the Nexus Build executable actually being used. The project must explicitly import and reference those settings. A project-local file with that module name takes precedence.

Run Nexus Build with /action=plan to inspect operations. Explicit tool paths are checked during planning; bare tool commands are resolved when launched.

The editor disagrees with the build

Confirm the selected project and nexusPascal.targets. Target values are case-sensitive. Verify that the editor's Nexus Build path identifies the same installation used by the terminal.

Nexus Script analysis uses target filtering. A reference to a filtered-out definition is an error, not an instruction to select another target.

For Pascal unit lookup, also review the Pascal language-server source paths and project context. Editor analysis is not a substitute for compiler validation.

Cached units or packages are rejected

Use a matching Nexus Pascal compiler, RTL, compiled units, and package SDK. Rebuild incompatible cached artifacts; do not rename upstream .ppu files to .nxu. See Nexus Pascal packages.

Debugging fails to start

Check the program filename, working directory, and debugger type nexus. Build the application with debug information. If source paths changed, supply a sourceMap. See Debugging.

Installation or emulator problems

Setup records commands and results in its installation state under <root>/.nx/setup/<product-id-key>/setup.log. An integration failure can leave installed files available for repair.

Emulator startup needs usable acceleration: Windows Hypervisor Platform or Linux KVM with appropriate device access. Setup reports startup failure separately from a successful Nexus installation. It does not erase existing virtual-device data to repair a launch failure.

When reporting a problem, include the command, selected targets, tool versions, and relevant error output. Omit credentials and unrelated configuration.