View Single Post
  #29   Spotlight this post!  
Unread 02-06-2015, 15:07
heydowns's Avatar
heydowns heydowns is offline
Registered User
AKA: Jeff Downs
FRC #1511 (Rolling Thunder)
Team Role: Mentor
 
Join Date: Jan 2006
Rookie Year: 2005
Location: Ra-Cha-Cha
Posts: 142
heydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond repute
Re: New tool for C++ Programming for old cRIOs

Quote:
Originally Posted by Crossle86 View Post
Yes, the FRC C++ tools. Would not work and after I added the C++ tools, it worked. All seems good except for the two errors that appear whenever I open a project: g++ not found in Path and gcc not found in path. Been all over the net looking at this issue and tried all kinds of fixes with no joy. It all seems to work so been ignoring those errors...but if you have a solution that would be nice.
Right. Those should not impact anything, except being slightly obnoxious.
They stem from the way the project is built up where Eclipse's build system tries (too) early to build the project, before the project has been fully configured internally with the toolset (which never invokes g++/gcc by those names). The error is recorded and never cleared.

The toolset does attempt to clear out those errors and force an initial build when the project has completed all configuration though and in all my tests this works here (you'll see the error briefly upon creation of a new project, then it will go away as soon as the rebuild is done, about 20 seconds later on my personal and all our school machines).

You should be able to select those errors in the list, right click, and delete them and they should not reappear.


Also whilst I am here - we have not forgotten about the "space in workspace path" problem noted earlier in the thread. Just have not had time yet to address it.
Reply With Quote