|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
No consyole feedback when deploying with eclipse
Whenever I try to deploy code to the ROBOrio with eclipse, I do not get anything in the console window. Also, when I build, I get the errors "Program GCC not found in PATH" and "Program G++ not found in PATH." I was told that these errors should be ignored and are not the problem. The code will not deploy. I tried uninstalling the toolchain and the NI update, and neither of these work. Has anyone else had this issue?
Thanks! |
|
#2
|
|||
|
|||
|
Re: No consyole feedback when deploying with eclipse
So you click WPILib Deploy in the menu and you see nothing at all in the Eclipse Console?
|
|
#3
|
||||
|
||||
|
Re: No consyole feedback when deploying with eclipse
that is correct.
|
|
#4
|
|||
|
|||
|
Re: No consyole feedback when deploying with eclipse
Check your Riolog window. Go to Window->Show View->other...
In the resulting "Show Window" pop-up, selec "General" then "Riolog" and click "OK". The Riolog window will show up as a tab next to the Console. Build results still go to the console, but printf et al go to the Riolog window. |
|
#5
|
|||
|
|||
|
Re: No consyole feedback when deploying with eclipse
I do not believe "Program GCC not found in PATH" and "Program G++ not found in PATH." are safe to ignore. They indicate the toolchain is not being found and without that your program is not being compiled. Try adding the path to the toolchain to your System PATH environment variable. Should be something like:
C:\frc\bin; I believe this is mentioned on the ScreenStep C++ installation page somewhere. |
|
#6
|
||||
|
||||
|
Re: No consyole feedback when deploying with eclipse
Quote:
Those errors about "gcc" and "g++" are from the base eclipse package trying to get default values for new system projects and will only cause issues if you want to develop for your local machine instead of the RoboRIO. |
|
#7
|
|||
|
|||
|
Re: No consyole feedback when deploying with eclipse
I stand corrected. We ran across the same errors (I think it was just the 2 errors, I don't recall the 'arm-frc...' error) on one of our installs (Win7, 64 bit, non-admin user account) and found the path to be missing. When the path to the toolchain was added the errors went away. We assumed that was the cause, though it is possible something else was changed as well.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|