Add Docker-based macOS build workflow and stabilize SD image assembly
buildbrain
This repository includes:
- linux-brain, u-boot-brain, nkbin_maker and boot4u as submodules
- Useful build targets in Makefile
- r3build.toml to watch changes that occur in submodules
Confirmed environments
- Debian 10 (buster) amd64
- Debian 11 (bullseye) amd64
- macOS 26.5 (Tahoe) arm64-apple-darwin25.5.0 via Docker
Getting Started
-
Install dependencies.
$ sudo apt install build-essential bison flex libncurses5-dev gcc-arm-linux-gnueabi gcc-arm-linux-gnueabihf libssl-dev bc lzop qemu-user-static debootstrap kpartx libyaml-dev python3-pyelftools -
Clone this repository with recursive clone enabled.
$ git clone --recursive git@github.com:brain-hackers/buildbrain.git- If you've cloned it without
--recursive, run following command:
$ git submodule update --init --recursive - If you've cloned it without
-
Install uuu.
- Follow the instruction and build
uuuexecutable. - Put
uuuwhere the PATH executable points to.
- Follow the instruction and build
Build U-Boot
-
Run
make udefconfig-sh*to generate.config.- For Sx1:
make udefconfig-sh1 - For Sx6:
make udefconfig-sh6 - For x1:
make udefconfig-h1
- For Sx1:
-
Run
make ubuildto build whole repository and generateu-boot.sboru-boot.bin.- i.MX283 loads a packed U-Boot executable called
u-boot.sb.
- i.MX283 loads a packed U-Boot executable called
Inject U-Boot into i.MX283 in recovery mode
-
Follow
Build U-Bootprocedure to make U-Boot binary. -
Run
make uuu
Build and make NK.bin
-
Follow
Build U-Bootprocedure to make U-Boot binary. -
Run
make nkbin-maker. -
To make
nk.bin, runmake nk.bin.- nkbin_maker packs
u-boot.binintonk.bin.
- nkbin_maker packs
Build and deploy boot4u
-
Run
make boot4u -
Create index.din and copy AppMain.bin
mkdir /path/to/your/sd/1st/partition/App/boot4utouch /path/to/your/sd/1st/partition/App/boot4u/index.dincp boot4u/AppMain.bin /path/to/your/sd/1st/partition/App/boot4u/
Build Linux
-
Run
make ldefconfigto generate.config. -
Run
make lbuildto generatezImage. -
Confirm that
linux-brain/arch/arm/boot/zImageexists.
Build a Debian rootfs
-
Run
make ldefconfig lbuild. -
Run APT cache in background (mandatory):
make aptcache. -
Run
make brainux. -
Run
make image/sd.img -
Confirm that
image/sd.imgis built and burn it to an SD card.
Build a Buildroot rootfs
Buildroot rootfs aims to be the most lightweight rootfs for experimental use. make buildroot_rootfs runs the defconfig target for rootfs-only build and then builds the rootfs tarball and a CPIO archive for initramfs. make image/sd_buildroot.img makes a bootable SD image in image directory like the typical Brainux SD image.
If you want to customize the build of Buildroot, cd into buildroot and use the following targets:
make menuconfigto change the configurationmaketo build the rootfs (-joption might give you extra speed)
image/sd_buildroot.img target expects presence of the tarball at buildroot/output/images/rootfs.tar. You'll have to clean and rebuild every time you change the Buildroot's config before making the SD image.
Docker build
You can build everything in Docker instead of preparing native Linux cross toolchains on your host.
Prerequisites
- Docker Desktop (or Docker Engine) with Linux containers enabled
- A clone with submodules initialized
Steps
-
Build the builder image.
make docker-build -
Build complete SD image in stages (recommended for macOS to avoid daemon crashes).
make docker-sd-image-fullThis runs three separate containers in sequence, which distributes resource load and prevents Docker Desktop daemon from running out of memory. Alternatively, run each stage independently:
make docker-kernel make docker-rootfs make docker-sd-imageNote: On macOS Docker Desktop, the combined memory footprint of kernel compilation, rootfs staging, and loop device operations can exceed the default VM allocation (~2-4 GB). Breaking into stages allows the daemon to garbage collect between steps.
Note:
make docker-rootfs(and thusmake docker-sd-image-full) always deletes and recreates the named volumebuildbrain-brainux-rootfsbefore building, so each rootfs build starts from a clean slate. To delete the volume manually between runs usemake docker-volume-rm.
Direct Docker commands (advanced)
For macOS, run in stages and use a named volume for the rootfs.
[!NOTE] Why a named volume for the rootfs? macOS APFS (the host filesystem behind Docker bind mounts) cannot create device files (
mknod), may stripsetuidbits, and does not faithfully preserve all Linux filesystem attributes. If the Debian rootfs is stored on APFS the result looks complete but will fail to boot — systemd cannot exec as PID 1 because the rootfs is subtly broken. Themake docker-*targets below storebrainux/in a Docker named volume (buildbrain-brainux-rootfs), which lives inside the Docker Desktop Linux VM on an ext4 filesystem and supports full Linux semantics.
# Create a named volume for the rootfs (Linux ext4 inside the Docker Desktop VM)
$ docker volume create buildbrain-brainux-rootfs
# Stage 1: kernel (bind mount is fine for source + outputs)
$ docker run --rm --platform linux/amd64 -v "$PWD":/work -w /work buildbrain-builder:local \
bash -lc "make ldefconfig && make lbuild"
# Stage 2: rootfs (must use named volume, NOT a bind mount for brainux/)
$ docker run --rm --platform linux/amd64 --privileged -e CI=true \
-v buildbrain-brainux-rootfs:/work/brainux \
-v "$PWD":/work -w /work buildbrain-builder:local \
bash -lc "make brainux"
# Stage 3: image assembly (mount the same named volume so cp -a reads from Linux ext4)
$ docker run --rm --platform linux/amd64 --privileged \
-v buildbrain-brainux-rootfs:/work/brainux \
-v "$PWD":/work -w /work buildbrain-builder:local \
bash -lc "make -C nkbin_maker clean all && make IMG_BUILD_JOBS=1 image/sd.img"
On Linux with sufficient resources, you can run all steps in one container (no named volume needed on a native Linux host):
$ docker run --rm --platform linux/amd64 --privileged -e CI=true -v "$PWD":/work -w /work buildbrain-builder:local \
bash -lc "make ldefconfig lbuild && make nkbin-maker && make brainux && make image/sd.img"
Other useful Docker recipes:
make docker-ubootto build U-Bootmake docker-kernelto build Linux kernelmake docker-volume-createto (re-)create the rootfs named volumemake docker-volume-rmto delete the rootfs named volume and reclaim its disk space
Known issues
If you use GCC 10 for the host compiler, make ubuild may fail.
To complete build, open /u-boot-brain/scripts/dtc/dtc-lexer.lex.c or /u-boot-brain/scripts/dtc/dtc-parser.tab.c then comment out YYLTYPE yylloc;
Watch changes in submodules & auto-build
-
Run
make setup-devto prepare a Python venv to watch code changes. Namely;- Python 3 venv in
env - r3build command in the env
- Python 3 venv in
-
Run
r3build. It'll detect the changes you make and builds the corresponding executable automatically.
What's r3build?
r3build is a smart file watcher that aims to provide hot-reloading feature like Web frontend development.