English | 中文

smart-build is a standalone build system for RT-Thread Smart. It provides one command-line interface for machine configuration, package selection, kernel and root filesystem builds, incremental task execution, build manifests, and QEMU smoke checks.

The project runs from its source tree. Build outputs, downloaded archives, toolchains, and the RT-Thread source tree are kept outside version control.

The currently implemented root filesystem image format is ext4. FAT and romfs appear in the configuration interface but are not yet buildable.

• Python 3.10 or newer.
• A compatible toolchain from Env SDK, a configured TOOLCHAIN_PATH, or the repository's downloads/toolchains/ cache. Missing downloadable versions can be installed with smart-build toolchain install.
• RT-Thread Env package scripts under ~/.env/tools/scripts and a package index under ~/.env/packages/packages.
• An RT-Thread source tree available as the repository-root rt-thread path, usually as a symbolic link.
• Host build tools reported by smart-build doctor.
• The QEMU system binary declared by the selected board for smoke tests.

Install the Python package in editable mode:

python -m pip install -e .

./smart-build doctor
./smart-build toolchain list
./smart-build menuconfig
./smart-build build all
./smart-build qemu-smoke

To select a machine without changing the workspace configuration:

./smart-build --machine qemu-virt-riscv64 doctor
./smart-build build kernel --machine qemu-virt-riscv64

Build results are written below build/<machine>/. Downloaded source archives and installed toolchains are stored below downloads/.

When a root-level buildroot/ checkout is available, buildroot menuconfig and buildroot import can create best-effort smart-build packages. If the checkout is missing, buildroot menuconfig asks whether to shallow-clone the latest Buildroot repository first. Existing packages are skipped and failures do not stop later imports. Imported package metadata keeps upstream network URLs; source archives are downloaded only by the normal smart-build package build. Import success means metadata was generated, not that cross-compilation has been verified.

Before compiling the kernel, smart-build synchronizes its defconfig to the RT-Thread BSP and runs ~/.env/tools/scripts/pkgs --force-update. Kernel packages and their versions are selected by the RT-Thread kernel configuration, not by smart-build package metadata. Unrecorded package directories that would participate in the kernel build are removed with a warning.

./smart-build --help
./smart-build doctor
./smart-build toolchain list
./smart-build toolchain install --yes
./smart-build menuconfig
./smart-build configure kernel
./smart-build configure package:curl
./smart-build configure package:webclient
./smart-build buildroot menuconfig
./smart-build buildroot import
./smart-build build all
./smart-build build kernel
./smart-build build kernel --verbose
./smart-build build rootfs
./smart-build graph
./smart-build qemu-smoke
./smart-build clean
./smart-build download-clean

Independent RT-Thread SCons packages with native Kconfig, such as webclient, use the package configure command to open their RT-Thread package options.

Before tasks run, build analyzes the machine, toolchain, selected packages, and task graph. Interactive terminals show a live plan: progress bar while package metadata is loaded; redirected output prints each planning phase. Planning ends with plan: ready N tasks. Normal builds then show a colored progress bar in interactive terminals and report completed tasks above it, for example build: [2/12] toolchain:check: skipped. Redirected output uses the same status format without colors or terminal control sequences. Successful and skipped tasks do not print log paths or log contents. build --verbose prints planning items, task context, task logs, and log paths to the terminal. When the target includes the RT-Thread kernel, smart-build runs its compile step with scons --verbose to show the complete compiler and linker commands.

build --dry-run currently prints a placeholder task plan. It is useful for a high-level preview, but it is not guaranteed to match every task in a real build.

• Getting started
• Configuration
• Command reference
• Using packages
• Adding a package
• Package description reference
• Supported boards
• Adding board support
• Root filesystem support
• Adding a root filesystem type
• Troubleshooting
• Compatibility and current limitations
• Contributing

No project license has been selected in this repository yet. A license must be added before distributing the project for general third-party use.