Installing on macOS¶
The recommended method for installing PROS on all platforms is now using our VS Code extension. Instructions for this can be found on the Getting Started page.
If you do not want to use VS Code, the method below will allow you to install the old, deprecated fork of Atom we call the PROS Editor or the CLI by iteslf.
If you are an advanced user looking to install the PROS CLI through Python pip, check out the Installing the CLI section below.
- If you do not already have Homebrew installed, install it by following the instructions on their site. This will take a while, and may prompt you to follow some additional instructions.
- Once you have Homebrew installed, run
brew tap osx-cross/arm && brew install arm-gcc-binto register a repository with Homebrew that contains the toolchain used to build PROS projects, and then install the toolchain.
brew tap purduesigbots/prosto register the PROS Homebrew repository with Homebrew.
brew install --cask pros-editorto install the PROS Editor (the CLI will also be installed). This may also take a while.
- (Optional) If you are planning to use the Vision Sensor, you will likely need
to also install the VEX Vision Utility to set up signatures. Run
brew install vcs-visionto do this. Once installed, you’ll be able to run the program by looking for “vcs_vision” in Spotlight.
- That’s it! You can now start using PROS.
If you do not want to use the PROS Editor, and instead intend to use only the PROS CLI, substitute the command in step 4 with the following:
brew install pros-cli.
If you don’t want to use Homebrew to install PROS, you can install all the components manually.
Install the toolchain¶
- Download the latest version of the GNU Arm Embedded Toolchain for macOS from their site.
- Once you have downloaded the toolchain, double click the file to extract its contents.
- Copy the contents of the
gcc-arm-none-eabi-X-20XX-qX-updatefolder (where the Xs are numbers specific to the version you downloaded) to another folder, for example
- Now you will need to link the toolchain binaries to somewhere that the system
will be able to find them. There are two ways to do this:
- (recommended, easy to update) run
mkdir -p /usr/local/bin/pros-toolchain && ln -s /usr/local/lib/pros-toolchain/bin/* /usr/local/bin/pros-toolchain(replacing
/usr/local/lib/pros-toolchainwith the path to the folder you made in step 4 above). Finally, add
/usr/local/bin/pros-toolchainto the end of your
- (easier, less easy to update) simply run
ln -s /usr/local/lib/pros-toolchain/bin/* /usr/local/bin.
- (recommended, easy to update) run
Install the CLI¶
- Install Python 3.6 or higher from the Python website or through Homebrew.
python3 -m pip install pros-cli
You can also install the CLI using the Python Wheel file (.whl) we distribute with our releases. Once downloaded, you can install from the .whl file directly using pip.
Install the Editor¶
This section is optional if you intend to use an editor other than the PROS Editor.
Minimum macOS version: 10.8 Minimum Python version: 3.6
RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment.
If you are using the PROS Editor, open up your init script (File > Init Script) and add the following two lines:
process.env.LANG = 'en_US.utf-8' process.env.LC_ALL = 'en_US.utf-8'
If you are just using the CLI at the Terminal:
- Open up your Terminal.
cdto make sure you’re in your home directory.
touch .bash_profileto make sure you have a shell login configuration file.
- Edit the
~/.bash_profilefile in your preferred editor (you can also run
open -e .bash_profileto edit it in TextEdit), adding the following two lines at the end:
export LANG="en_US.utf-8" export LC_ALL="en_US.utf-8"
. .bash_profileto reload the file for the current session.
/bin/sh: intercept-c++: command not found
This issue should be fixed for PROS CLI versions > 3.1.2
- Check your PROS CLI version by running
pros --version. If your version is <= 3.1.2, try updating first to check if that solves your problem. If not, continue with step 2.
- Follow steps 1-4 listed above for those using the CLI only. In step 4, however, add the following line instead (replacing the Xs with the numbers found in step 1):