commit | b5b46ca609a6a87660a3d7ad197f99ba80bf8292 | [log] [tgz] |
---|---|---|
author | Brian Silverman <brians> | Sun Mar 13 01:14:17 2016 -0500 |
committer | Brian Silverman <brians> | Sun Mar 13 01:14:17 2016 -0500 |
tree | 6310597fe1134490ef423acf25bccc4866533836 | |
parent | 41e3b7967b39e9db84a222f70e284cccdae3241a [diff] |
Remove stupid wpilib forwarding target It's silly to need to use NO_BUILD_AMD64 for //aos/... Change-Id: I103b3c3a0f5cfb72c081c5aafef624cf0533acb0
This is FRC Team 971's main code repository. There are README*
files throughout the source tree documenting specifics for their respective folders.
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:
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).
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.
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/
.
apt-get install python libpython-dev bazel ruby clang-format-3.5 clang-3.6 gfortran libblas-dev liblapack-dev python-scipy python-matplotlib
Some useful Bazel commands:
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.
bazel build --cpu=roborio --compilation_mode=opt //y2015/...
bazel run --cpu=roborio --compilation_mode=opt //y2015:download roboRIO-971.local