Gitiles
Code Review Sign In
realtimeroboticsgroup.org / RealtimeRoboticsGroup / test / aa06a20df3fe7d71decbd41d4e9e84c4f1e29c78
commitaa06a20df3fe7d71decbd41d4e9e84c4f1e29c78[log] [tgz]
authorBrian Silverman <brians>Sat Feb 04 16:29:41 2017 -0800
committerBrian Silverman <brians>Sat Feb 04 16:31:17 2017 -0800
tree0681c9394f0763a501abf107e62163a1f7360c11
parentabb3d19efd7954f01062d2e55109fc7deae80f78 [diff]
parentf7f267a91e70db6e5f62b09d88f0d02f15c904e8 [diff]
Add this year's WPILib source

Umodified so far. BUILD files and changes to make that all work are
coming.

Change-Id: Iba1b60b5fe027e4d83e0d844089f42f473cea133
tree: 0681c9394f0763a501abf107e62163a1f7360c11
  1. aos/
  2. build_tests/
  3. compilers/
  4. debian/
  5. doc/
  6. frc971/
  7. third_party/
  8. tools/
  9. vm/
  10. y2012/
  11. y2014/
  12. y2014_bot3/
  13. y2015/
  14. y2015_bot3/
  15. y2016/
  16. y2016_bot3/
  17. y2016_bot4/
  18. y2017/
  19. .clang-format
  20. .gitignore
  21. LICENSE.txt
  22. NO_BUILD_AMD64
  23. NO_BUILD_ROBORIO
  24. README.md
  25. 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 to add reviewers. If you just upload a change without adding any reviewers, it might sit around for a long time before anybody else notices it. 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 libpython-dev bazel ruby clang-format-3.5 clang-3.6 gfortran libblas-dev liblapack-dev python-scipy python-matplotlib
  1. Allow Bazel's sandboxing to work: Follow the direction in doc/frc971.conf.

Some useful Bazel commands:

  • Build and test everything (on the host system):
bazel test //... -- $(cat NO_BUILD_AMD64)
bazel build --cpu=roborio //... -- $(cat NO_BUILD_ROBORIO)

The NO_BUILD_{AMD64,ROBORIO} files contain lists of the targets which are intentionally not built for the various CPUs.
  • 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:download roboRIO-971.local