Convert all WPILib motors into Strongback motors #46
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… classpath. TODO: Fix the hard coded paths.
Note that wpilib's build files ONLY look in the wpilib folder, this means that any jars not located in this folder will not be compiled. Thus, we must include json.jar, strongback.jar, and any talon libraries in this folder (these are not visible in the commit). Additionally, json.jar was removed from this project as it is not longer needed in this repo.
These build targets did nothing but call another target, so they were removed.
…y URL. Why? Well, wpilib requires ALL user library jars to be placed in wpilib/user/java/lib, which is a folder that this repo does not "own". Additionally, there is no easy or elegant way to move jars into this directory. The simplest solution I can think of is copying jars into the file from this repo, but I really don't want to include too many jar files in this repo. Addionally, the site that was previously downloading WPILib did not include the cpp or tools folders (which might be nessecarry in order to deploy, I'm not sure). Instead, I decided to download the wpilib folder directly from a repo that we "own" (currently it's set to a repo I just made, but we can switch it over to the FRC1076 organization). As a bonus, this means that updating WPILib is easy, you update WPILib on a machine through eclipse, and then you push these changes to GitHub. Then, anyone can pull these updates without having to go through the same troubles. It also means that dependencies are easier to share between projects (and only one person needs to ever download these dependencies).
Override Strongback's incorrect buildpath for test compilation. Why?
Strongback assumes that the correct class path is ${classpath}, which
does have WPILib.jar and NetworkTables.jar. However, this doesn't include
any user libraries (like Strongback itself!). Instead we add the path "classpath.path",
which is the correct path that wpilib uses for compilation and includes user libraries.
(the ${classpath} property is defined in ${wpilib.dir}/java/current/ant/build.properties.)
TestRobot.java has been updated to test these changes.
This commit fixes possible conflicts due to files being imported more than once, as that could cause some overriding properties to not override properly.
This commit also replaces the TeleopCommand with a temporary arcade drive. This drive should be later placed into the current TeleopCommand (or possibly moved into a subsystem instead).
Since the new robot only has two motors (left and right), there is no need to keep FrontBackMotors. All instances of FrontBackMotors have been removed from the codebase. Additionally, DriveLeftRight was removed as that used only FrontBackMotors
This was referenced Jan 27, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Blocked by PR #42