From 54057258665b6cc3576c7f782a38ed9307bc862c Mon Sep 17 00:00:00 2001 From: Thomas Hebb Date: Fri, 1 Jan 2021 11:51:52 -0800 Subject: [PATCH] Don't silently eat errors in Python requirements install It's questionable that dependencies get installed automatically during the build in the first place, but since they do we should at least fail the build with an error if installation fails. This makes the current CI issue on macOS much clearer to diagnose. --- make_scripts_riscv/project.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/make_scripts_riscv/project.mk b/make_scripts_riscv/project.mk index b2c94d6f..66c41c7b 100644 --- a/make_scripts_riscv/project.mk +++ b/make_scripts_riscv/project.mk @@ -187,7 +187,7 @@ all: ifeq ("$(OS)","Windows_NT") else ifeq ("$(CONFIG_CHIP_NAME)", "BL602") - @cd $(BL60X_SDK_PATH)/image_conf;python3 -m pip install -r requirements.txt; python3 flash_build.py $(PROJECT_NAME) $(CONFIG_CHIP_NAME) + @cd $(BL60X_SDK_PATH)/image_conf && python3 -m pip install -r requirements.txt && python3 flash_build.py $(PROJECT_NAME) $(CONFIG_CHIP_NAME) endif endif @echo "Building Finish. To flash build output."