custom FW repos code generation process toolset #5817

rusefi · Jan 23, 2024 · e1be1f2 · e1be1f2
1 parent c4b88f5
commit e1be1f2
Show file tree

Hide file tree

Showing 4 changed files with 10 additions and 4 deletions.
diff --git a/...llen/alphax-2chan/compile_alphax-2chan.sh → ...s/hellen/alphax-2chan/compile_firmware.sh b/...llen/alphax-2chan/compile_alphax-2chan.sh → ...s/hellen/alphax-2chan/compile_firmware.sh
diff --git a/...ellen121nissan/compile_hellen121nissan.sh → ...ellen/hellen121nissan/compile_firmware.sh b/...ellen121nissan/compile_hellen121nissan.sh → ...ellen/hellen121nissan/compile_firmware.sh
diff --git a/...nfig/boards/hellen/uaefi/compile_uaefi.sh → ...g/boards/hellen/uaefi/compile_firmware.sh b/...nfig/boards/hellen/uaefi/compile_uaefi.sh → ...g/boards/hellen/uaefi/compile_firmware.sh
diff --git a/misc/jenkins/compile_other_versions/compile.sh b/misc/jenkins/compile_other_versions/compile.sh
@@ -16,16 +16,22 @@ echo "Entering $SCRIPT_NAME with folder $BOARD_DIR and bundle name $BUNDLE_NAME"
 
 [ -n $BUNDLE_NAME ] || { echo "BUNDLE_NAME parameter expected"; exit 1; }
 
-COMPILE_SCRIPT="compile_$BUNDLE_NAME.sh"
-
 cd firmware
 bash clean.sh
 cd ..
 
-root_dir=$(pwd)
-
 cd firmware/$BOARD_DIR
 pwd
+
+COMPILE_SCRIPT="compile_$BUNDLE_NAME.sh"
+if [ -f $COMPILE_SCRIPT ]; then
+  # detailed compile script is useful for instance when same board has multiple MCU targets
+  echo "[$COMPILE_SCRIPT] found!"
+else
+  echo "Using default script name..."
+  COMPILE_SCRIPT="compile_firmware.sh"
+fi
+
 echo "Invoking $COMPILE_SCRIPT"
 
 bash $COMPILE_SCRIPT