kenfox
20-01-2013, 12:19
When re-generating C++ code, newly added subsystems and components are not added to Robot.cpp. The bug is caused by a typo in "export/cpp/files.yaml":
--- resources/export/cpp/files.yaml (revision 619)
+++ resources/export/cpp/files.yaml (working copy)
@@ -27,7 +27,7 @@
modifications:
autonomous: ${exporter-path}CommandBasedRobot-autonomous.cpp
constructors: ${exporter-path}CommandBasedRobot-constructors.cpp
- initializanion: ${exporter-path}CommandBasedRobot-initialization.cpp
+ initialization: ${exporter-path}CommandBasedRobot-initialization.cpp
You can work around the problem by manually editing the initialization section of your Robot.cpp and changing "ID=INITIALIZATION" to "ID=INITIALIZANION". Or if you haven't made any changes to Robot.cpp, you can delete it and let Robot Builder generate it from scratch. The bug only happens when updating it.
The tracker at FIRST Forge doesn't seem open for bug reports, so I hope the right people see it here.
--- resources/export/cpp/files.yaml (revision 619)
+++ resources/export/cpp/files.yaml (working copy)
@@ -27,7 +27,7 @@
modifications:
autonomous: ${exporter-path}CommandBasedRobot-autonomous.cpp
constructors: ${exporter-path}CommandBasedRobot-constructors.cpp
- initializanion: ${exporter-path}CommandBasedRobot-initialization.cpp
+ initialization: ${exporter-path}CommandBasedRobot-initialization.cpp
You can work around the problem by manually editing the initialization section of your Robot.cpp and changing "ID=INITIALIZATION" to "ID=INITIALIZANION". Or if you haven't made any changes to Robot.cpp, you can delete it and let Robot Builder generate it from scratch. The bug only happens when updating it.
The tracker at FIRST Forge doesn't seem open for bug reports, so I hope the right people see it here.