Try the RobotBuilder tool, defining the subsystems, sensors, and actuators of this year's robot. This is not to distract anyone from aos, just to try it out and see what other teams are using. Also it looks very handy for robot hardware checkout and PID tuning.
Cf docs http://wpilib.screenstepslive.com/s/3120/m/7882/l/88538-overview-of-robotbuilder
Cf video demo http://www.youtube.com/user/bradamiller
git-svn-id: https://robotics.mvla.net/svn/frc971/2013/trunk/src@4101 f308d9b7-e957-4cde-b6ac-9a88185e7312
diff --git a/robot_builder/Robot2013/.wrmakefile b/robot_builder/Robot2013/.wrmakefile
new file mode 100644
index 0000000..a1dd7f8
--- /dev/null
+++ b/robot_builder/Robot2013/.wrmakefile
@@ -0,0 +1,48 @@
+# The file ".wrmakefile" is the template used by the Wind River Workbench to
+# generate the makefiles of this project. Add user-specific build targets and
+# make rules only(!) in this project's ".wrmakefile" file. These will then be
+# automatically dumped into the makefiles.
+
+WIND_HOME := $(subst \,/,$(WIND_HOME))
+WIND_BASE := $(subst \,/,$(WIND_BASE))
+WIND_USR := $(subst \,/,$(WIND_USR))
+
+all : pre_build main_all post_build
+
+_clean ::
+ @echo "make: removing targets and objects of `pwd`"
+
+%IDE_GENERATED%
+
+-include $(PRJ_ROOT_DIR)/*.makefile
+
+-include *.makefile
+
+main_all : external_build $(PROJECT_TARGETS)
+ @echo "make: built targets of `pwd`"
+
+# entry point for extending the build
+external_build ::
+ @echo ""
+
+# main entry point for pre processing prior to the build
+pre_build :: $(PRE_BUILD_STEP) generate_sources
+ @echo ""
+
+# entry point for generating sources prior to the build
+generate_sources ::
+ @echo ""
+
+# main entry point for post processing after the build
+post_build :: $(POST_BUILD_STEP) deploy_output
+ @echo ""
+
+# entry point for deploying output after the build
+deploy_output ::
+ @echo ""
+
+clean :: external_clean $(CLEAN_STEP) _clean
+
+# entry point for extending the build clean
+external_clean ::
+ @echo ""