Ah. Never mind. I need to use a library to connect out the
serial port for the Arduino Terminal. I’m using jSSC which is
LGPL. There really isn’t an alternative and I’m not sure I want
to get into the game of making a new one.
Doug.
That’s essentially what it is no matter where it ends
up. I’ve only kept it separate to deal with the GPL
licensing on the toolchain. But I think p2 gives us ways
to deal with that.
The other benefit is that I hope it opens the door to
adding more ports like this, for the Raspberry Pi and Pi
2 for example. If you have an open cross toolchain, it
should be easy to add support for it. And the more
hobbyists we get in Eclipse and CDT, the better for our
community IMHO.
Doug.
I
haven't looked at the code on github, but by
bringing that code to CDT directly, does it boil
down to adding support to CDT for Arduino
development?
Sounds like a nice addition for CDT, +1
Hey gang,
As I’ve mentioned here a few times and
will be talking about at the CDT Day at
EclipseCon, I’m building some plug-ins
that extend the CDT, Remote, and LaunchBar
to support development for Arduino using
C++. I’ve been building it out on my
github site as part of my Wascana
activities of supporting hobbyists who
want to use CDT and want the toolchain
installed with it.
The Arduino work is a bit special
because I want to use it as an exemplary
implementation of such extensions and
really want to talk about it in the CDT
context. The challenge will be the
toolchain install. At the moment, I pull
the toolchain at build time using some
maven magic, but I want to avoid legal
issues of the bits being packaged together
(even though commercially vendors are OK
doing that). I think I can work some p2
magic and grab the bits from somewhere
else at install time. I’d then put this
work up in the Eclipse Marketplace.
Are there any objections to me bringing
the plug-in source over and putting it
into the CDT and adding it to the CDT
builds?
Doug.
