Gitiles
Code Review Sign In
realtimeroboticsgroup.org / RealtimeRoboticsGroup / test / c2b7774e944971de75d95a59434b75e4b828d008
commitc2b7774e944971de75d95a59434b75e4b828d008[log] [tgz]
authorAustin Schuh <austin.linux@gmail.com>Thu Nov 26 16:18:27 2015 -0800
committerAustin Schuh <austin.linux@gmail.com>Thu Nov 26 16:18:29 2015 -0800
treecdf895e245a58e8e53760d86cea53bddc658051f
parente6df5ee5520e9fbac439f5e048ce9ac9ba17512b [diff]
UpdateObserver now takes U as an argument.

This supports running UpdateObserver without a control loop better.

Change-Id: I62a304fa192604bc5b400c8bbf5191971a8534cc
5 files changed
tree: cdf895e245a58e8e53760d86cea53bddc658051f
  1. aos/
  2. build_tests/
  3. debian/
  4. doc/
  5. frc971/
  6. output/
  7. third_party/
  8. tools/
  9. y2014/
  10. y2014_bot3/
  11. y2015/
  12. y2015_bot3/
  13. .clang-format
  14. .gitignore
  15. LICENSE.txt
  16. README.md
  17. WORKSPACE
README.md

Introduction

This is FRC Team 971's main code repository. There are README* files throughout the source tree documenting specifics for their respective folders.

Access to the code

The main central location for our code is our Gerrit server at https://robotics.mvla.net/gerrit. To get a copy of the code on your computer to work with, follow these steps:

  1. Contact Michael Schuh to get an SVN account.
  2. Go to Gerrit and create an account.
  3. Contact Brian Silverman with your SVN username to get access to the code in Gerrit.
  4. Go to the 971-Robot-Code project in Gerrit and run the command. Running the clone with commit-msg hook command will save you trouble later.

To learn more about git, see git(1) (man git or git(1) (especially the NOTES section).

Code reviews

We want all code to at least have a second person look over it before it gets merged into the master branch. Gerrit has extensive documentation on starting reviews. TL;DR: git push origin HEAD:refs/for/master and then click on the link. git-review can make the upload process simpler.

Building the code

The currently supported operating system for building the code is amd64 Debian Jessie. It is likely to work on any x86_64 GNU/Linux system, but that's not at all well-tested.

We use Bazel to build the code. Bazel has extensive docs and does a nice job with fast, correct increment rebuilds.

Steps to set up a computer to build the code: 0. Set up the required APT repositories: Download frc971.list and llvm.org.list and put them in /etc/apt/sources.list.d/.

  1. Install the required packages:
apt-get install python bazel ruby clang-format-3.5 clang-3.6
  1. Allow Bazel's sandboxing to work

Some useful Bazel commands:

  • Build and test everything (on the host system):
bazel test //...

This currently requires adding `-//{y2014,y2015,bot3,frc971}/wpilib/... -//aos/externals:wpilib` to avoid trying to build WPILib to work.
  • Build the code for a specific robot:
bazel build --cpu=roborio --compilation_mode=opt //y2015/...
  • Download code to a robot:
bazel run --cpu=roborio --compilation_mode=opt //y2015/prime:download roboRIO-971.local