rusefi/firmware/gen_live_documentation.sh

#!/bin/bash

rm gen_live_documentation.log

cd ../java_tools
./gradlew :config_definition_base:shadowJar
./gradlew :enum_to_string:shadowJar
cd ../firmware

java -DSystemOut.name=logs/gen_live_documentation \
 -cp ../java_tools/configuration_definition_base/build/libs/config_definition_base-all.jar \
 com.rusefi.ldmp.LiveDataProcessor integration/LiveData.yaml
[ $? -eq 0 ] || { echo "ERROR generating"; exit 1; }

java -DSystemOut.name=logs/gen_java_enum -cp ../java_tools/enum_to_string/build/libs/enum_to_string-all.jar com.rusefi.ToJavaEnum -enumInputFile console/binary/generated/live_data_ids.h -outputPath ../java_console/io/src/main/java/com/rusefi/enums
[ $? -eq 0 ] || { echo "ERROR generating live data ids"; exit 1; }

# live_data_ids.h is generated above so order of operations is important here!

./gen_enum_to_string.sh
Switch to Bash (#1585) * switch firmware to bash * switch unit_testts to bash * switch jenkins to bash 2020-07-09 07:27:20 -07:00			`#!/bin/bash`
partial manual pick of #1506 2020-06-18 09:41:14 -07:00
			`rm gen_live_documentation.log`

only:facilitating config reuse with non-bash consumers 2023-06-17 13:35:36 -07:00			`cd ../java_tools`
only:Split ConfigGenerator around trigger_defines.txt #5051 2023-06-17 19:26:31 -07:00			`./gradlew :config_definition_base:shadowJar`
only:CI to use tools from source code, also time to not have jar files in repo in the first place? 2023-06-17 14:16:01 -07:00			`./gradlew :enum_to_string:shadowJar`
only:facilitating config reuse with non-bash consumers 2023-06-17 13:35:36 -07:00			`cd ../firmware`

placing all logs into same folder 2021-10-23 17:18:09 -07:00			`java -DSystemOut.name=logs/gen_live_documentation \`
we are confusing gradle when we ask shadowJar output to look same as jar output #5966 2024-02-16 21:48:57 -08:00			`-cp ../java_tools/configuration_definition_base/build/libs/config_definition_base-all.jar \`
renaming tool 2022-10-28 00:44:39 -07:00			`com.rusefi.ldmp.LiveDataProcessor integration/LiveData.yaml`
we need to fail if generator fails 2021-10-16 17:43:44 -07:00			`[ $? -eq 0 ] \|\| { echo "ERROR generating"; exit 1; }`
automation around outputs section #197 datalog toolset 2021-11-28 14:04:46 -08:00
we are confusing gradle when we ask shadowJar output to look same as jar output #5966 2024-02-16 21:48:57 -08:00			`java -DSystemOut.name=logs/gen_java_enum -cp ../java_tools/enum_to_string/build/libs/enum_to_string-all.jar com.rusefi.ToJavaEnum -enumInputFile console/binary/generated/live_data_ids.h -outputPath ../java_console/io/src/main/java/com/rusefi/enums`
live_data_e part of the process was broken? 2023-01-15 02:55:54 -08:00			`[ $? -eq 0 ] \|\| { echo "ERROR generating live data ids"; exit 1; }`
only:simplifying scripts: gen_enum_to_string.sh is invoked only by gen_live_documentation.sh 2023-07-03 20:33:19 -07:00
			`# live_data_ids.h is generated above so order of operations is important here!`

we are confusing gradle when we ask shadowJar output to look same as jar output #5966 2024-02-16 21:48:57 -08:00			`./gen_enum_to_string.sh`