Make 2019 robot start again
The last time we deployed, we were using aos_downloader to start
everything. Now, we use the config. So update the config to match what
actually needs to be started.
Change-Id: I3d9bf5e1b0ca9b748f4279f69234954f54acb655
Signed-off-by: Austin Schuh <austin.linux@gmail.com>
diff --git a/y2019/y2019.json b/y2019/y2019.json
index 7a30be4..719925c 100644
--- a/y2019/y2019.json
+++ b/y2019/y2019.json
@@ -43,7 +43,36 @@
],
"applications": [
{
- "name": "drivetrain"
+ "name": "drivetrain",
+ "executable_name": "drivetrain.stripped"
+ },
+ {
+ "name": "trajectory_generator",
+ "executable_name": "trajectory_generator.stripped"
+ },
+ {
+ "name": "superstructure",
+ "executable_name": "superstructure.stripped"
+ },
+ {
+ "name": "server",
+ "executable_name": "server.stripped"
+ },
+ {
+ "name": "logger_main",
+ "executable_name": "logger_main.stripped"
+ },
+ {
+ "name": "joystick_reader",
+ "executable_name": "joystick_reader.stripped"
+ },
+ {
+ "name": "autonomous_action",
+ "executable_name": "autonomous_action.stripped"
+ },
+ {
+ "name": "wpilib_interface",
+ "executable_name": "wpilib_interface.stripped"
}
],
"imports": [