Other build systems

NativeLink speaks the standard Remote Execution API. If your build tool speaks the same protocol, you can point it at NativeLink without rewriting your build files.

Options

• Buck2 — use Buck2's built-in remote execution client with NativeLink as CAS, Action Cache, and executor.
• Siso — configure Chromium's Ninja replacement to use NativeLink through the RE API.
• Pants — enable remote cache reads and writes from pants.toml.
• BuildStream — point BuildStream artifact storage and remote execution at NativeLink.
• CMake with recc — wrap CMake compile actions with recc and share compile outputs through NativeLink.

Common NativeLink endpoint

The examples below assume a NativeLink server exposing CAS, Action Cache, execution, capabilities, and ByteStream on port 50051 with instance name main.

The BuildStream page follows the checked-in integration test, which uses the default empty instance on the same local port.

For a local Docker server, start with Getting Started → Setup. For the Buck2 integration test shape, see integration_tests/buck2/buck2_cas.json5.