rusefi-1/firmware/config/boards
GitHub build-firmware Action d215291ad5 Auto-generated configs and docs 2021-03-24 00:29:05 +00:00
..
frankenso
hellen Auto-generated configs and docs 2021-03-24 00:29:05 +00:00
kinetis Auto-generated configs and docs 2021-03-24 00:29:05 +00:00
me7_pnp rename setBoardConfigurationOverrides (#2479) 2021-03-22 14:15:09 -04:00
microrusefi rename setBoardConfigurationOverrides (#2479) 2021-03-22 14:15:09 -04:00
nucleo_f767 rename setBoardConfigurationOverrides (#2479) 2021-03-22 14:15:09 -04:00
nucleo_h743 rename setBoardConfigurationOverrides (#2479) 2021-03-22 14:15:09 -04:00
prometheus rename setBoardConfigurationOverrides (#2479) 2021-03-22 14:15:09 -04:00
proteus rename setBoardConfigurationOverrides (#2479) 2021-03-22 14:15:09 -04:00
skeleton rename setBoardConfigurationOverrides (#2479) 2021-03-22 14:15:09 -04:00
st_stm32f4 rename setBoardConfigurationOverrides (#2479) 2021-03-22 14:15:09 -04:00
subaru_eg33 Auto-generated configs and docs 2021-03-24 00:29:05 +00:00
STM32F407VET6_Black.bat
STM32F407VET6_Hellen_STM.bat
STM32F407VET6_Mini.bat
clean_env_variables.bat
clean_env_variables.sh deduplication in halconf (#2377) 2021-02-24 14:08:03 -05:00
common_make.bat
common_make.sh update all compile scripts to use available cores rather than a hardcoded value (#2425) 2021-03-06 12:55:46 -05:00
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