[Ken Streeter]

Originally Posted by prograid

As for your problem with the error parser, go to the project properties for your project and select C/C++ Build, then look through the tabs until you see the one with a list of error parsers. Make sure that the one with GCCError in the name is checked. If you want to be safe, just check all of them.

Originally Posted by Ken Streeter

I've tried that but haven't yet met with success. I'll try making a new project from scratch with mcc18 to see if a "Hello World" program works okay; another programmer on our team reported seeing the parser problems previously when importing old code into a new project. I'm hoping that starting from scratch may fix it...

I tried tweaking the error parsers settings within the IDE to lots of different configurations (all set, only C/C++ set, only make and C/C++ set, etc.) in attempts to get the error / warning message parsing to function. None of my attempts work. The only errors that show up are the "make" errors -- none of the line-specific errors show up in the "Problems" tab. I tried this both with our working Robot code and also with a "Hello World" program and had the same results in both cases. I was trying this with the newest compilation toolset I could find:

• Eclipse 3.2.1
• CDT 3.1.1
• MCC18 2.0.1 (from Team 254)

Since I had not been seeing this problem before doing toolset upgrades, I decided to try an older toolset. An older toolset works just fine! Here is the toolset that worked for me:

• Eclipse 3.1.2
• CDT 3.0.2
• MCC18 1.2.0 (from Team 254)

I tried determining which of the above changes was responsible for my problem, but haven't had time to try all of the combinations. I speculate that the problem may actually be due to an interplay between different pieces of the toolset, rather than being caused solely by one of the new components.

If anybody has been able to get error message parsing working correctly with the newer toolset I list above, I'd be glad to hear about it! At this point, however, I think our team is likely to proceed for our fall term software training with the above toolset that we have working, since we are likely to need to upgrade for the build season anyway.

--ken