Closed jianyicheng closed 1 year ago
Thanks @JianyiCheng, looks promising. Will give it a try. What do you think about removing the submodules and instead doing several "git clone" in the `build-cheri.sh" script? The trouble with the submodules is that cloning the repo becomes very expensive even when you don't want to enable CHERI.
OK. Will move them to the bash script.
Also wondering if we can use cheribuild's llvm
target (rather than sdk-riscv64-purecap
) to avoid building qemu, cheribsd, and gdb.
Also wondering if we can use cheribuild's
llvm
target (rather thansdk-riscv64-purecap
) to avoid building qemu, cheribsd, and gdb.
It might be possible, but we may need to change the makefile as well - last time I tried the make
command and it failed...
Shall we discuss the future road map of SIMTight to see if you will need CPU/OS in future works?
Looks very useful. Before merging, I'd like to see:
inc/Config.h
dropped.gdb
, cheribsd
, and qemu
(I tried the llvm
target and it worked for me; where you using the latest cheribuild
?).cheri-settings.sh
to add-cheri-tools-to-path.sh
, and normal-settings.sh
to remove-cheri-tools-from-path.sh
, and move these scripts to the cheri-tools
dir.build
to build-cheri-tools
; also fix the .PHONY
attribute for this rule.Done. Do you know how to make cheribuild
with LLVM only - I am not sure how to disable the others
Done. Do you know how to make cheribuild with LLVM only - I am not sure how to disable the others
Is it not just ./cheribuild.py llvm
?
Oh sorry. I did not find it in the help info... It has now been updated.
source scripts/normal-settings.sh
enables baseline environmentssource scripts/cheri-settings.sh
enables CHERI