View Single Post
  #5   Spotlight this post!  
Unread 12-21-2015, 11:16 PM
ozrien's Avatar
ozrien ozrien is online now
Omar Zrien
AKA: Omar
no team
Team Role: Mentor
 
Join Date: Sep 2006
Rookie Year: 2003
Location: Sterling Heights, MI
Posts: 516
ozrien has a brilliant futureozrien has a brilliant futureozrien has a brilliant futureozrien has a brilliant futureozrien has a brilliant futureozrien has a brilliant futureozrien has a brilliant futureozrien has a brilliant futureozrien has a brilliant futureozrien has a brilliant futureozrien has a brilliant future
Re: Problem with WPI Library

euhlmann wasn't wrong, it's a good idea to reindex when creating a new project so eclipse IDE knows to look at the latest WPILIB headers for IDE features that require it. Sometimes you will get parser errors because the index'd info is stale, but they look like real compiler-errors (red lines).

Yellow lines are warnings, red lines are errors.

EclipseCDT sometimes keep old errors/warnings around after you fix them. Once in a while I will go the project explorer, expand Binaries, and delete FRCUserProgram (this is the binary you are building). Then select all the warning and errors in the Problem tab and delete them. Then full build the project. This will cleanly update the errors/warnings. If FRCUserProgram comes back in the project explorer, then you're program built successfully.
http://www.chiefdelphi.com/forums/sh...63&postcount=5

The Console window also shows latest error output from the compiler, this streams the actual output of the compiler. The problems tab is the IDE's attempt to parse the output of the last build attempt (but it tends to forgot to clear sometimes).

Your latest looks good, compiles on my side.
Reply With Quote