Cargo FRC

A cargo subcommand for deploying your rust code.

Installation

In this package, run cargo install, assuming cargo's bin is in your PATH.

Usage

Add a config section like toml [package.metadata.frc] team-number = 114 rio-address = "10.1.14.2" target-dir = "target" executable-name = "digital_out" to your Cargo.toml.

• team-number - used to deduce the IP of the roborio if an override is not provided. Currently, this will try mDNS, USB, and the conventional static IP.
• rio-address - set the one and only IP cargo frc will try to deploy to
• target-dir - set the relative or absolute path of cargo's target directory. This is usually just "./target", but will vary for cargo workspaces.
• executable-name - set the name of the binary to deploy to the RIO. If not specified, the package.name key is used instead.

You can then run cargo frc deploy in your robot code package.

Limitations

Currently, you must deploy once with GradleRIO/ant/whatever at least once before cargo frc will work. As of yet, I have not figured out an easy way to fetch versioned shared libraries to deploy. Ideally I could use crates.io and associated versioning.

Roadmap

• [x] MVP to streamline wpilib testing and development
• [ ] Test windows support
• [ ] Deploy shared libraries
• [ ] Automatic debugging support with gdb and its server

License

This application and its source code are released under the GPLv3. By contributing, you license your contribution under the GPLv3. You also agree to have your contribution included in a future version of this library licensed under a future version of the GPL as released by the Free Software Foundation.