Build from VS Code

For a Nexus project, the extension invokes Nexus Build with the selected project and build/analysis targets. The build uses the same tool environment as a standalone command.

Explicit task

A normal VS Code process task is also useful when you want a visible, project-specific command. For the Hello example, save this as .vscode/tasks.json on Windows:

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "Build Hello",
      "type": "process",
      "command": "${config:nexusPascal.nxbuildPath}",
      "args": [
        "/action=build",
        "/project=${workspaceFolder}/Hello.nxproject",
        "/targetos=win64",
        "/targetcpu=x86_64",
        "/buildconfiguration=Debug"
      ],
      "group": {"kind": "build", "isDefault": true},
      "problemMatcher": []
    }
  ]
}

On Ubuntu, change /targetos=win64 to /targetos=linux. This explicit task fixes its own target arguments; the extension's generated Nexus tasks instead use the shared target selection.

Build configurations

BuildConfiguration selects matching Nexus Script definitions. The name Debug does not itself add compiler debug flags, and Release does not itself enable optimization. The project declares those settings.

Use separate output directories in the project when configurations must retain separate products.

Other project types

Nexus Build supports Pascal, LLVM C/C++, CMake, MSBuild, and MSVC operations. Their tool settings belong to the selected project/environment. Existing Lazarus adapters remain available for projects that explicitly use that toolchain; they are not prerequisites for Nexus projects.

See Nexus Build for dependencies, validation, and command-line use.