And that was not a small camel either, it was called eclipse.
And to no surprise, it started to throw tomatoes at me at once. Think of it, a camel being eaten throwing tomatoes at you...
Never the less I wanted to try it out, to give eclipse once again a chance to become the environment for existing old projects, to run and debug in linux environment. Once again since I have tried and used eclipse in several other occasions and failed. But there are some people claiming it to be THE environment for avr on linux. Well, we see...
After a couple of hours beating back on to the tomato throwing camel I got the avr plugin working. After yet some time I could create a project pointing to the existing source folder and build using existing makefile. Wonderfull.
But, Once it compiles the source it start throwing tomatoes again, this time by flushing the console with messages like
Plug-in de.innot.avreclipse.core.managedbuildsystem was unable to load class org.eclipse.cdt.managedbuilder.internal.scannerconfig.DefaultGCCScannerInfoCollector.
The build completes, though it also claims there is errors in build. But the code compiles just fine and generates well working binaries.
Any explanation from java lovers????