From 4e868c98dcb19ef65be28a290a863a8eb17d0181 Mon Sep 17 00:00:00 2001 From: KGSoong <144529387+KGSoong@users.noreply.github.com> Date: Sun, 21 Jan 2024 10:48:33 +0000 Subject: [PATCH] [BUILDING] make it clear for the user to set up path --- BUILDING.md | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/BUILDING.md b/BUILDING.md index b8262e245cf..8f8d970e8af 100644 --- a/BUILDING.md +++ b/BUILDING.md @@ -366,6 +366,15 @@ Since CHERI support is available only for a few platforms, verifying CHERI-C programs that use header files from the C standard library will require a setup of a C standard library for one of these platforms. +To obtain and install a CHERI sysroot, the +[cheribuild](https://github.com/CTSRD-CHERI/cheribuild) +tool is the recommended way: +``` +cheribuild.py cheribsd-riscv64-purecap disk-image-riscv64-purecap -d +``` + +Once the build completed, you'll find `cheri` directory in your HOME directory. + CHERI-enabled ESBMC defaults to the platform mips64-unknown-freebsd and expects the corresponding sysroot, the default of which can be configured by passing the CMake flags @@ -373,9 +382,6 @@ passing the CMake flags -DESBMC_CHERI_HYBRID_SYSROOT= -DESBMC_CHERI_PURECAP_SYSROOT= ``` -To obtain and install a CHERI sysroot, the -[cheribuild](https://github.com/CTSRD-CHERI/cheribuild) -tool is the recommended way: -``` -cheribuild.py cheribsd-mips64-hybrid disk-image-mips64-hybrid -``` +e.g. the 'path' should point to `$HOME/cheri/output/rootfs-riscv64-purecap`. As for the `rootfs-riscv64-purecap` part, you may want to use a diffrent directory if you used a different variant in the `cheribuild.py` command above. + +