build

Build BartonCore

Build Hierarchy

BartonCore has a layered build system. Each layer calls the one below it:

build.sh  (top-level convenience script)
  └── cmake  (configure + build)
        └── build-matter.sh  (Matter SDK, invoked automatically by CMake when needed)

• build.sh is the human-friendly entry point that handles configuration and parallel builds.
• cmake --build build is the preferred command for incremental rebuilds after code changes.
• build-matter.sh builds the Matter SDK. CMake invokes it automatically — you almost never need to run it manually.

Incremental Rebuild (most common)

After modifying source files, rebuild with:

cmake --build build

This only recompiles changed files and is fast. Use this as the default build command.

Full Build From Scratch

For a first-time build or a clean rebuild:

./build.sh

This configures CMake (using the dev profile by default) and builds the entire project in parallel. It creates the build/ directory if it doesn't exist.

Options:

• ./build.sh -d — Delete the CMake cache before reconfiguring (clean reconfigure)
• ./build.sh -C <cache-file> — Use a custom CMake initial-cache file instead of the dev profile
• ./build.sh --no-initial-cache — Don't use any initial-cache; use default public options

You can append CMake flags directly:

./build.sh -DBCORE_ZIGBEE=OFF

Development Build Profile

By default, build.sh uses config/cmake/platforms/dev/linux.cmake which enables:

CMake Configuration Flags

Pass these with -D to cmake or appended to ./build.sh:

Subsystem Flags

Build Option Flags

Example: Build Without Zigbee

cmake --build build  # if already configured
# or to reconfigure:
./build.sh -d -DBCORE_ZIGBEE=OFF

Build Output

• Libraries and executables are in build/
• Reference app binary: build/reference/barton-core-reference
• Matter SDK installation: build/matter-install/

Error Recovery

If a build command fails with a tool-not-found error (e.g., cmake: command not found, make: command not found, gcc: command not found):

1. Check if /.dockerenv exists
2. If it does NOT exist, stop and tell the user: "Build tools are not available. Please run inside the BartonCore development container."
3. If it does exist, the error is a genuine build problem — read the error output and diagnose