Java code getting g++/gcc errors in Eclipse from c++ scanner?

[s-taylor]

I had an error-free code base earlier today.
I finally got around to GIT-ifying the repo (Thanks, GitHub!), and after re-importing the git clone into Eclipse, the auto-scanning "Problems" tab suddenly started reporting a C++ related *error* condition:

Program "arm-frc-linux-gnueabi-g++" not found in PATH

with reported location being:
Project Properties, C++ Preprocessor Include.../Providers, [CDT Cross GCC Built-in Compiler Settings] options

I dug around in the Project Properties, and there are plenty of Java references but nothing even remotely related to c++, and certainly nothing with the hierarchy specified in the Location string.

I'm not sure what I could have done to cause this, and it doesn't seem to prevent the java code from compiling to the point of deployment (I have no robot access today).... but it worries me, especially since it is an error condition that might prevent something from being deployed tomorrow!

Anyway... how did this c++ scanning end up in my java-only project? I did accidentally click on 'c++' in RobotBuilder sometime in the last couple of days and had to go into the project and delete out the c++ files; it's possible something is left hanging behind I suppose. I looked in the build.xml and don't see anything.

Before I go reverting back to earlier pre-git versions and trying to diff/reconstruct a large number of changes... any suggestions?

Thanks...
-Scott

[s-taylor]

No solution yet, but more data:
One of the git commits added .cproject, .settings\language.settings.xml, and .settings\org.eclipse.cdt.managedbuilder.core.pref s files in addition to the project files I was editing.

These all have c++ and CDT related references in them, so something happened at that time unrelated to the intended edits. I'm just not sure what I need to 'undo'!

I tried renaming the above files and restarting eclipse to see if that solved the problem, but... it didn't.

[s-taylor]

Case: Closed?

Debugging with an eclipse expert offline, it seems that:

1) I needed to delete the three dotfiles mentioned in my previous reply (this is ok because the project is entirely Java so the files were irrelevant, and

2) also needed to explicitly/manually delete the errors from the Problems tab (they were sticky, even across eclipse restarts)

The running theory is that hitting the RobotBuilder C++ button overlaid both Java and C++ code in the workspace, and re-importing the project into Eclipse happened before I had eliminated 100% of the C++ vestiges... so part of the system believed there was C++ code to parse, while the .project file for eclipse believed that it was purely a Java "Nature" once the remaining C++ files were removed.

Hopefully posting this solution will help anyone else who manages to accidentally paint themselves into a corner.
Now that I've gotten the paint washed off my shoes... back to getting the students ready for the season!

Cheers,
-Scott