custom-board-bundle-sample-.../firmware/config/boards
Matthew Kennedy 761e65c710 make board config override actually usable (#2508)
* new function

* hellen

* MRE

* proteus

* put those function declarations in a reasonable place

* put the comment back

* weak

* move that to a reasonable place

Co-authored-by: Matthew Kennedy <makenne@microsoft.com>
2021-03-31 14:46:50 -04:00
..
frankenso
hellen make board config override actually usable (#2508) 2021-03-31 14:46:50 -04:00
me7_pnp
microrusefi make board config override actually usable (#2508) 2021-03-31 14:46:50 -04:00
nucleo_f767
nucleo_h743 make board config override actually usable (#2508) 2021-03-31 14:46:50 -04:00
prometheus
proteus make board config override actually usable (#2508) 2021-03-31 14:46:50 -04:00
st_stm32f4 make board config override actually usable (#2508) 2021-03-31 14:46:50 -04:00
subaru_eg33
STM32F407VET6_Black.bat
STM32F407VET6_Hellen_STM.bat
STM32F407VET6_Mini.bat
clean_env_variables.bat
clean_env_variables.sh
common_make.bat
common_make.sh
readme.md

readme.md

See misc/jenkins/compile_other_versions/run.bat which is executed by build server.

See https://rusefi.com/build_server/

By definition, BOARD_NAME is a folder in firmware\config\boards

One BOARD_NAME could be producing a number of artifacts via compile_$BUNDLE_NAME.sh scripts

Work in progress: SHORT_BOARDNAME becomes BUNDLE_NAME