Crates.io | cargo-frc |
lib.rs | cargo-frc |
version | 0.4.0 |
source | src |
created_at | 2018-05-29 08:14:10.689942 |
updated_at | 2019-01-16 19:43:17.474801 |
description | A cargo extension for deploying rust code to FRC robots. |
homepage | |
repository | https://github.com/Lytigas/first-rust-competition |
max_upload_size | |
id | 67569 |
size | 22,466 |
A cargo subcommand for deploying your rust code.
In this package, run cargo install
, assuming cargo
's bin is in your PATH
.
Add a config section like
[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 totarget-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.
wpilib
testing and developmentgdb
and its serverThe contents of this repository are distributed under the terms of both the MIT license and the Apache License (Version 2.0). By contributing, you agree to license your contribution under these terms.
See LICENSE-APACHE, LICENSE-MIT, for details.