PoC to build freedom-metal and scl-metal w/ LLVM & CMake/Ninja
The recommended way is to use a Docker environment.
To run the command natively (w/o Docker), remove docker/bin/dock.sh and the first argument from
the following example.
The following command should pull in all the required containers and test that the LLVM toolchain is available.
It is expected to take some time on the first run (about 1.8 GB to download).
docker/bin/dock.sh build clang --versionSubsequent runs should start immediately as the container material is preserved in Docker images.
-
One or more BSPs should be selected. The supported BSPs can listed as
ls -1 bsp/
-
Build RV32 and RV64 QEMU BSPs
docker/bin/dock.sh build scripts/buildall.sh qemu-sifive_e_rv32 qemu-sifive_e_rv64
Alternatively, it is possible to build for a single build type and a single target, as in:
docker/bin/dock.sh build scripts/build.sh debug qemu-sifive_e_rv32
The output files are still available in the host directories, below
build/. -
Rebuild the project in development mode
docker/bin/dock.sh build '(cd build/qemu-sifive_e_rv32/debug && ninja)'
QEMU is used to run unit tests.
A special QEMU for RISC-V targets is required: one that support the sifive_fdt generic targets
that instantiates the whole virtual machine from a DTB file. It is available through a Docker
image, or can be rebuilt to run it natively on any host.
-
Tests all generated unit test executables
docker/bin/dock.sh utest scripts/utestall.sh build/
-
Alternatively, it is possible to test a single build type of a single target, as in:
docker/bin/dock.sh utest scripts/utest.sh -d bsp/qemu-sifive_e_rv64/dts/qemu.dts \ build/qemu-sifive_e_rv32/debug
Note that to run QEMU natively (w/o Docker), it is possible to use the
-eoption to specify the directory where QEMU-FDT resides.
A GitHub Actions script is used to build and run unit tests for several QEMU virtual targets.
.
├── CMakeLists.txt # Top level CMake file to build the project
├── bsp # BSP directory, with DTS file and BSP-specific header files
├── cmake # CMake configuration and macros
│ ├── Platform # RISC-V platform definition
│ ├── files # CMakeFiles.txt copied to the existing metal and scl-metal directories*
│ ├── macros.cmake # Useful CMake macros to help buildint the project
│ └── riscv.cmake # RISV-C toolchain configuration
├── docker # All docker files
│ ├── bin # Docker script to run build and test scripts from Docker containers
│ ├── conf # Docker configuration, define versionned image for each tasks
│ └── src # Dockerfiles to build the images, the toolchains, ...
├── metal # freedom-metal framework
├── scl-metal # scl-metal submodule
├── scripts # Useful scripts to automate tasks
│ ├── build.sh # Script to build the project for a single BSP
│ ├── buildall.sh # Script to build all the BSPs in all possible configurations
│ ├── funcs.sh # Common functions used by other scripts
│ ├── utest.sh # Script to execute the unit test of a single BSP
│ └── utestall.sh # Script to execute all built unit tests
├── tests # Unit test files (SCL-metal tests and QEMU tests)
│ ├── hello # Simplest test to check an application may be executed
│ ├── qemu # HCA tests which are not yet part of SCL
│ └── scl-metal # test-scl-metal submodule
└── unity # Unit test framework
*: as this project is forked from the official freedom-metal and scl-metal repositories,
which do not yet use CMake (nor Ninja) to build binaries, a couple of CMakeFiles.txt files are
maintained out-of-tree and copied into the existing directories when CMake is invoked. It should
ease maintenance and integration. CMakeFiles.txt files should not be committed into the
sub-module repositories.
Docker images are built on top of Alpine Linux, as it is the smallest distribution, and enables to build the smallest image files.
All shell scripts should be POSIX-compliant, i.e. should not use bash-isms.