Does PROS 3.2.0.1 actually run on Windows?

[Steven_Luke]

I have been trying to install PROS 3.2.0.1 on Win 10 for a few days with zero success. This is the error when I build:

c:\Projects\VexVRC\PROS\TestRos>pros make
Creating cold package with libc,libm,libpros,okapilib Error: Failed to build
[ERRORS]
/bin/sh: line 1: arm-none-eabi-g++: command not found
make: *** [common.mk:229: bin/cold.package.elf] Error 127

The same error when doing a make from the command line or through Atom. I tried with and without Windows Subsystem for Linux installed, same error. I found this bug report:

Build fails in both cli and in atom

and added my comment, but that doesn’t look to have any constructive response (though it is 5 months old and for a previous version of the software).

So my question is: has anyone actually installed PROS 3.1.4 or 3.2.0.1 on a fresh (never seen PROS before) Windows 10 computer successfully? If so, any help getting it to work?

Thanks,
Steve

[sazrocks]

Have you tried the list of fixes for known issues in this post?

PROS CLI 3.2.0 - Wireless Terminal! (IMPORTANT)

Known Issues (please read this ENTIRE post!) All platforms There is currently a bug related to uploading projects wirelessly (i.e. through a controller) to a brain with the latest firmware. We’re working on a fix and will post another release as soon as we have it Windows If you upgraded PROS at any point between 2:30AM and 3:00PM (EDT) on March 19 2021, you likely ran into various problems including (but not necessarily limited to): missing start menu shortcut to the PROS Editor unable to r…

[Daryl]

Take a look at this part spcifically

@hotel

UPDATE : if you are unable to build projects, please add %PROS_TOOLCHAIN%\gcc-arm-none-eabi-10-2020-q4-major\bin to your PATH environment variable as a temporary workaround (guide ).

[Steven_Luke]

Yeah, that fixed it. I saw it earlier and thought it only applied to the 3.2.0.0 version from that small time frame. But adding the path to g++ to the PATH variable worked. Thanks