I read an interesting bit of commentary lately on Eclipse’s impact on the Embedded industry…
What a difference a decade makes. In 1999, every embedded systems tool provider who had an RTOS and a set of tools supported them with a proprietary integrated development environment (IDE), tying everything into a neat tightly connected tool chain.
Now, one of the last holdouts – Texas Instruments – has abandoned its proprietary IDE in favor of one based on open source Eclipse. The transition is complete, with virtually every major embedded software vendor supporting their own implementation of Eclipse, including Wind River, Green Hills, QNX, Lynux Works, Rapid Logic and Mentor Graphics, among others…
This is good news for Eclipse given that I view the embedded community tough as nails. These are folks that have an affinity for TCL and autotools. Ok, maybe that’s a generalization, but I still have nightmares dealing with autoconf and obscure m4 messages that were impossible to debug. In the commentary, the author asks, “What are some of the other things we can look forward to?” That’s a good question and I’m not really sure, but I have some things on my mind.
The Resource architecture that Eclipse uses has been criticized for being overly Java-centric and constraining for some use cases. The e4 incubator explored this problem and developed some concrete improvements to the resource model to address these problems. We will review and polish those changes and back-port them to Helios stream where appropriate.
Flexible resources should enable a new set of workflows for embedded developers that are used to other environments like Visual Studio. Here’s a webinar if you want to know more.
Another thing that may be interesting to embedded developers is the Linux Tools project at Eclipse which aims build on top of CDT and integrate popular native development tools such as the GNU Autotools, Valgrind, OProfile, RPM and Systemtap. If you browse the Linux Tools new and noteworthy page, you can easily see the great progress their making.
Can anyone think of other things that embedded developers can look forward to?