David Vo

On the units note, perhaps it's time to bite the bullet and add a dependency on `uom`? (Or should we go with a different units crate?)

Given we don't have anything that would be generic over Gyro, maybe adding the trait is a bit premature.

I suspect doing it this way setting a relevant CC environment variable would be more compatible, especially with the `cc` crate.

Note to self: add some sort of test to ensure using this actually compiles.

It looks like the HAL is getting a refactor for I2C, so this should wait until after we update for 2021 beta.

We should install the FRC toolchain in the standard place (`~/wpilib/$YEAR`) and point project cargo configs to whatever `arm-frc$YEAR-linux-gnueabi-gcc` we can find, if you ask me.

Although… I feel the alternative of #87 would be better. Then we don't break if `.cargo/config` is checked into git, and it opens up the possibility of running simulation too.

> I'm not sure I agree that 1.76 MB is large (if binary size is what you mean) wpilib-sys-0.4.0 is a bit over 5 MiB, making it larger than encoding_rs....

I've gone and created a repo for frc-chipobject-sys as well. That might end up with other dependencies itself - I've also created an ni-visa-sys repo, and I've noticed @connorworley has...

[You can't have multiple crates link to the same library](https://doc.rust-lang.org/cargo/reference/build-scripts.html#the-links-manifest-key), so we're going to need a -sys package either way.