tools/ci.sh: Manually install picotool for rp2 builds.
If picotool is not installed, it's fetched and built when compiling each rp2 board. And the "develop" branch of picotool is used instead of a release. Installing it manually using the "master" branch means the latest released version is used (instead of a possibly unstable development version), and also makes building each rp2 board a little faster. Signed-off-by: Damien George <damien@micropython.org>
This commit is contained in:
parent
3805e65ed3
commit
e34412f0f4
1 changed files with 11 additions and 0 deletions
11
tools/ci.sh
11
tools/ci.sh
|
|
@ -22,6 +22,15 @@ function ci_gcc_riscv_setup {
|
|||
riscv64-unknown-elf-gcc --version
|
||||
}
|
||||
|
||||
function ci_picotool_setup {
|
||||
# Manually installing picotool ensures we use a release version, and speeds up the build.
|
||||
git clone https://github.com/raspberrypi/pico-sdk.git
|
||||
(cd pico-sdk && git submodule update --init lib/mbedtls)
|
||||
git clone https://github.com/raspberrypi/picotool.git
|
||||
(cd picotool && mkdir build && cd build && cmake -DPICO_SDK_PATH=../../pico-sdk .. && make && sudo make install)
|
||||
picotool version
|
||||
}
|
||||
|
||||
########################################################################################
|
||||
# c code formatting
|
||||
|
||||
|
|
@ -62,6 +71,7 @@ function ci_code_size_setup {
|
|||
gcc --version
|
||||
ci_gcc_arm_setup
|
||||
ci_gcc_riscv_setup
|
||||
ci_picotool_setup
|
||||
}
|
||||
|
||||
function ci_code_size_build {
|
||||
|
|
@ -355,6 +365,7 @@ function ci_renesas_ra_board_build {
|
|||
|
||||
function ci_rp2_setup {
|
||||
ci_gcc_arm_setup
|
||||
ci_picotool_setup
|
||||
}
|
||||
|
||||
function ci_rp2_build {
|
||||
|
|
|
|||
Loading…
Reference in a new issue