After exchanging impressions around Arduino and CDT with Jan, Liviu
and Johan I have the following suggestion to go forward:
- CDT continues to concentrate on "platform" things, i.e. on
improving CDT capabilities to be extended for particular hardware
family like Arduino.
- Sloeber formulates/contributes the new extensions/capabilities to
the CDT/Platform to reduce effort duplication and focus on
Arduino-specific things.
- CDT removes Arduino-related parts that duplicates Sloeber, and
provides discovery hooks to simplify Sloeber installation for C/C++
package if user is looking for Arduino support.
This will be hardly possible without transparent and open
collaboration between all of us: let's use this mailing list and
bugzilla to discuss technical details .
Regards,
AF
31.12.2019 18:17, Alexander Fedorov
пишет:
Hi Jonah,
This New Year gift is quite huge :)
I'll try to sort out what is going on there. If you can introduce
me to Liviu and/or Jan that would be very helpful.
Regards,
AF
P.S.
It's exciting to know that famous "GNU MCU Plug-ins" goes under
Eclipse Foundation umbrella!
31.12.2019 17:45, Jonah Graham пишет:
Hi Alexander,
Excellent - I don't want to deprecate/delete stuff
that has a reasonable chance of being maintained in the
future. Would you like to take over managing the Marketplace
entry for Arduino - it was last updated for CDT 9.3 https://marketplace.eclipse.org/content/eclipse-c-ide-arduino
There are a few other TODOs that need someone to run
point on:
- reaching to Jan Baeyens to figure out if Sloeber (https://github.com/Sloeber/arduino-eclipse-plugin)
and CDT communities can work better together. The Sloeber
plug-ins are still actively maintained based on the commit
history, but I don't know current state/thoughts from Jan.
- Resolve where Arduino plug-ins should live going
forward - with the new iot.ecdt project (https://projects.eclipse.org/projects/iot.ecdt -
formerly GNU MCU Plug-ins) there is an overlap of embedded
toolchain management.
- Reviewing/triaging Arduino bugs as they come in
(bugzilla search link)
Do we need to hurry with the decision? I don't think the
Arduino support code is something specific from the
quality perspective to be deprecated above all :)
Especially if people are still interested to use it.
I suggest to think about the component lifecycle from the
SimRel perspective:
- incubation (not yet in the SimRel)
- mature (a part of SimRel)
- legacy (already out of SimRel)
- retired (no downstream, archived)
As far as I know there is a plan to have more strict
checks for SimRel contributions. And as a result there
will be a diffusion between "mature" and "legacy" sets of
components.
And yes, I plan to touch the Arduino set of bundles as
well, but this is not in the top of my list ATM.
Regards,
AF
31.12.2019 3:31, Jonah Graham пишет:
Hello folks,
Unfortunately it seems the issues
in Arduino plug-ins are unlikely to be addressed any
time soon. Therefore I suggest we deprecate the
Arduino plug-ins and schedule them for deletion.
The topic of deleting deprecated code has come up
a few times recently and at the moment CDT does not
have a fixed plan or policy on how to do this. I
plan to make a proposal at some point, but if anyone
has ideas on how they would like to see the project
handle deleting deprecated code please do share.
And, if someone does intend to work on the
Arduino plug-ins, please speak up or let me know
off-list if you want to have a discussion first of
what is involved.
A while back Doug spent quite a bit of effort
adding specific Arduino support into CDT. There
are a few plug-ins that integrate Eclipse CDT
with the Arduino ecosystem, allowing for example
to download Arduino packages.
At the moment this set of bundles is not
being maintained by any active commiter. People
are still using it, and bugs are being reported
against it. The latter is a very big positive as
I see it as it means that users are interested
enough to report bugs against the software -
some even with workarounds and detailed
instructions on how to reproduce.
Can someone have a look at some of these:
Bug
558307 - Project clean rule unable to
remove file (contains a probable fix)