Build and Deploy Script #24
Merged
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
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.
This scripts allows for a quicker way for users to build and deploy their code to the robot. Instead of a really long
mbed-clicommand, use is now./builddeploy [fname]where[fname]is an optional folder name. Without an argument, this script checks formbed-greenteaand if it is installed, will use it to deploy. If not, it will copy the compiled binary to the robot in the default location in the ubuntu filesystem on the lab computers. With an argument, the script ignoresmbed-greenteaand copies the compiled binary to that folder.Example use-case for the optional
[fname]argument: Windows Subsystem for Linux (WSL) does not supportudev, whichmbed-greenteauses. Users can mount the robot into the ubuntu filesystem then deploy to it from WSL using this argument.