custom-board-bundle-sample-.../firmware/config/boards
rusefillc 70f65e0652 Hellen GDI 2021-05-14 11:00:18 -04:00
..
frankenso testing yaml automation 2021-05-07 15:34:48 -04:00
hellen Hellen GDI 2021-05-14 11:00:18 -04:00
kinetis gen_config.sh code duplication #2451 2021-05-11 22:00:36 -04:00
me7_pnp rename setBoardConfigurationOverrides (#2479) 2021-03-22 14:15:09 -04:00
microrusefi Revert "lua on f407 (#2646)" 2021-05-09 18:25:50 -04:00
nucleo_f767 rename setBoardConfigurationOverrides (#2479) 2021-03-22 14:15:09 -04:00
nucleo_h743 make board config override actually usable (#2508) 2021-03-31 14:46:50 -04:00
prometheus fix multi-serial-port insanity (#2476) 2021-03-28 09:06:36 -04:00
proteus Proteus legacy vs. non-legacy F7 (#2657) 2021-05-08 18:44:19 -04:00
skeleton remove intermediate buffer (#2668) 2021-05-10 08:01:24 -04:00
st_stm32f4 make board config override actually usable (#2508) 2021-03-31 14:46:50 -04:00
subaru_eg33 Auto-generated configs and docs 2021-05-10 12:32:55 +00:00
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