Gitiles
Code Review Sign In
realtimeroboticsgroup.org / RealtimeRoboticsGroup / test / 45bdd4322368f4adff41bf1e7e0b6dce5100ff53
commit45bdd4322368f4adff41bf1e7e0b6dce5100ff53[log] [tgz]
authorBrian Silverman <bsilver16384@gmail.com>Fri Mar 23 22:50:42 2018 -0400
committerBrian Silverman <bsilver16384@gmail.com>Mon Mar 26 03:21:40 2018 -0400
treeb3f0429b7b7f72fc2c094de433aeb4fe7902a61d
parent4f8c6a7531e49105b5790b1658e0e3d27087496a [diff]
Add sleeps so teensy_loader_cli works reliably for me

The whole idea of this program's "wait for all the Teensys we can find"
operation is fundamentally racy. At some point, I should really redo it
completely... For now though, just add sleeps to make it work on
machines where people care.

Change-Id: Iad8ad2c2dc7a95ac75bdf43950ff344a05923d8d
1 file changed
tree: b3f0429b7b7f72fc2c094de433aeb4fe7902a61d
  1. aos/
  2. build_tests/
  3. compilers/
  4. debian/
  5. doc/
  6. frc971/
  7. motors/
  8. third_party/
  9. tools/
  10. vm/
  11. y2012/
  12. y2014/
  13. y2014_bot3/
  14. y2016/
  15. y2017/
  16. y2017_bot3/
  17. y2018/
  18. .clang-format
  19. .gitignore
  20. LICENSE.txt
  21. README.md
  22. setup_roborio.sh
  23. 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:

  1. Set up the required APT repositories: Download frc971.list and llvm.org.list and put them in /etc/apt/sources.list.d/.
  2. Install the required packages:
apt-get install -t jessie-backports openjdk-8-jdk
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 //...
bazel build --cpu=roborio //...
  • 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