GradleRIO now has both Java and Native (C,C++) support in the root repository. This repository is discontinued.
Managing FRC C++ Projects, the Gradle way. Build, Develop and Deploy your FRC Code on any system, without the need for eclipse or administrative priviledges.
Unlike the standard FRC Development Tools, GradleRIO-C can be run on any system, even if they're locked down (like school PCs). This includes installing
the C++ toolchain (with the exception of debian linux, which requires sudo and/or apt access). The only requirement is the Java Virtual Machine to run Gradle itself, a Command Line, and an Internet Connection.
Replace gradlew with ./gradlew if you're on Mac or Linux
gradlew install_frc_toolchain will install the FRC C++ Toolchain, allowing you to build for the RoboRIO (note: while this is available on linux, it is best to install it yourself with the instructions here as it requires sudo access)
gradlew build will build your FRC Code
gradlew build deploy will build and deploy your FRC Code. Can also be run without build as gradlew deploy
gradlew restart_rio_code will restart user code running on the RoboRIO
gradlew clion will generate a CMakeLists.txt file for the Clion IDE. CLion w/ GradleRIO info can be found here.
gradlew cleanClion will delete all Clion associated files (e.g. CMakeLists.txt, .idea and cmake-build-debug)
Run gradlew tasks --all for more information.
GradleRIO will deploy to the RoboRIO through the following preference list:
1: mDNS (roborio-TEAM-frc.local)
2: USB (172.22.11.2)
3: Static IP (10.TE.AM.20)
The addresses for mDNS and Static IP can be changed in the buildscript.
Download the Quick Start Sample Project and edit it to your own accord. You can get examples here. Feel free to download them into your own project.
Put the following at the top of your build.gradle file
plugins {
// Replace latest-version with the latest version available.
id "jaci.openrio.cpp.gradle.GradleRIO-C" version "latest-version"
}
apply plugin: "cpp"You can copy-paste this install instruction from here
You can now setup your project just like any other Gradle C++ project.
You can get examples here. Feel free to download them into your own project.
Example (barebones) build.gradle below.
plugins {
id "jaci.openrio.cpp.gradle.GradleRIO-C" version "latest-version"
}
apply plugin: "cpp"
model {
frc {
team = "5333"
}
components {
my_program(FRCUserProgram) { // This is your program, my_program
targetPlatform "roborio-arm" // Build on the RoboRIO
sources.cpp {
source.srcDirs "src" // Where your .cpp files are stored
exportedHeaders.srcDirs "include" // Where your .h / .hpp files are stored
lib library: "wpilib", linkage: "static" // Compile with WPILib
lib library: "talonSrx", linkage: "static" // Compile with TalonSrx (CTRLib)
lib library: "navx", linkage: "static" // Compile with NavX
}
}
}
}Full GradleRIO-C Spec
plugins {
id "jaci.openrio.cpp.gradle.GradleRIO-C" version "latest-version"
}
apply plugin: "cpp"
// You can use Visual Studio for development and Gradle for building if you so desire.
// my_programVisualStudio to generate the Visual Studio 2010+ solution file
apply plugin: "visual-studio"
model {
frc {
team = "5333"
// The below options are optional. Values are the defaults
deployTimeout = 3 // Timeout (in seconds) when trying to find the RoboRIO on the network
deployDirectory = "/home/lvuser" // Directory to deploy to on the RoboRIO
rioIP = "10.53.33.20" // IP Address of the RoboRIO. This is automatically calculated from team number
rioHost = "roborio-5333-frc.local" // Hostname of the RoboRIO. This is automatically calculated from team number
robotCommand = "./my_program" // Script to run when booting the RoboRIO. This is automatically calculated based on the components below
runArguments = "" // Arguments to add to robotCommand. No effect if robotCommand is manually set
}
// This block is entirely optional. If not specified, it will use the WPILib from the WPILib Maven Repository and the default options
// NOTE: If you plan to use WPI from a Git repo, the FRC Toolchain Bin directory must be on your System PATH. If you installed
// on linux (or without GradleRIO), this is already done. If you installed on Windows or Mac with gradlew install_frc_toolchain,
// you must set your path before building, as WPILib's Git Repo does not look in ~/.gradle/gradlerioc/toolchain/<platform>/bin
// for the cross-compiling toolchain
wpi {
git = true // Set to true to use Git instead of the WPI Maven (github/wpilibsuite/allwpilib)
gitVersion = "3784b66" // Commit, Branch or Tag to checkout before building
eclipsePlugins = true // Set to true to use Local WPILib instead of the WPI Maven
local = true // Set to true if you want to use the WPILib libraries from a local path on your filesystem
localDirectory = file('libs/wpi') // Set this to where you have extracted the WPILibC Zip file (subdirs: lib, include). Must be set if local is true
// Maven is the default provider for the WPILib library
mavenBranch = "development" // Set which branch of the WPILib Maven to use. By default, this is 'release'
wpilibVersion = "2017.1.1-beta-3" // Set which version of WPILib to use from the Maven. By default, this is '+' (latest release)
halVersion = "2017.1.1-beta-3" // Set which version of the HAL to use from the Maven. By default, this is the same as mavenWpilib
wpiutilVersion = "1.0.2" // Set which version of WPIUtil to use from the Maven. By default, this is '+' (latest release)
ntcoreVersion = "3.1.2" // Set which version of NTCore to use from the Maven. By default, this is '+' (latest release)
cscoreVersion = "0.9.1-beta-3" // Set which version of CSCore to use from the Maven. By default, this is '+' (latest release)
talonSrxVersion = "4.4.1.9" // Set which version of CTRLib (Talon SRX) to use from the maven. By default, this is '+' (latest release)
navxVersion = "3.0.323" // Set which version of NavX to use from the maven. By default, this is '+' (latest version)
}
// Use this block to add libraries that have been prebuilt (i.e. device libraries, or other code)
// If you're building a library from source, it is better to add that as a dependency or as another component.
// If the library uses GradleRIO, use the multi_project example. If it doesn't, you can add the sources as shown
// in the custom_library example.
// This block is optional.
libraries {
some_lib(LibraryPrebuilt) {
headers "some_lib/include"
staticFile "some_lib/some_lib.a"
sharedFile "some_lib/some_lib.so"
}
}
components {
// This is where you define your actual C++ binary
my_program(FRCUserProgram) {
targetPlatform "roborio-arm" // Build using the RoboRIO Toolchain
sources.cpp {
source {
srcDirs "src" // Where your .cpp files are stored
}
exportedHeaders {
srcDirs "include" // Where your .h/.hpp files are stored
}
lib library: "wpilib", linkage: "static" // Compile with WPILib
lib library: "talonSrx", linkage: "static" // Compile with TalonSrx
lib library: "navx", linkage: "static" // Compile with NavX
lib library: "some_lib", linkage: "static" // From our libraries {} block
}
}
}
}GradleRIO-C supports the Windows Subsystem for Linux, a Beta feature that can be run with Windows 10. For this to work, however, you need the following requirements:
The following packages are required to be installed on WSL assuming a clean image:
sudo apt-get install git build-essentialsudo apt-get install gcc-multilib g++-multilibPlease note that, as of current, the Windows Subsystem for Linux does NOT support the FRC Toolchain. This may change for the 2017 season, however using the 2016 branch is not possible. Sorry.