Hi together,
i recently found that the good old GNU ARM Eclipse Plugin got some serious development progress.
http://gnuarmeclipse.livius.net/blog/
May be it's a good thing to integrate this in chibistudio or integrage chibios projects and so on in this plugin. Not only to have more comfort in using eclipse but also to lower the maintainance effort on ChibiStudio.
regards
Tec
ChibiStudio and GNU ARM Eclipse Plugin
-
tecnologic
- Posts: 124
- Joined: Tue Jan 10, 2012 8:42 am
- Has thanked: 21 times
- Been thanked: 5 times
- Giovanni
- Site Admin
- Posts: 14891
- Joined: Wed May 27, 2009 8:48 am
- Has thanked: 1202 times
- Been thanked: 996 times
Re: ChibiStudio and GNU ARM Eclipse Plugin
Hi,
Nice project but I can see several reasons to not do that, let me explain my point.
Apparently that plugin focuses on managed build, I prefer to stick to makefiles because those are way easier to maintain. When I change a path or add a driver then I just have to change one .mk file and all projects are fine. Considering the number of projects part of ChibiOS this is not a small thing. Updating Keil and IAR projects is a PITA for this same reason (this is why there are few examples of those).
Project templates are nice but probably incompatible with ChibiOS because different startup, vectors and scatter files. This could confuse users, I would expect to start a new ChibiOS project using the templates but that would not be the case.
In general, if I start supporting one environment what about EM:Blocks, Atollic, Crossworks, CoIDE, Ride7 and all the others?
I prefer a neutral approach to development environments, however, nothing forbids installing the GNU ARM plugins on ChibiStudio or ChibiOS plugins on any other Eclipse-based environment. Initially I tried to provide examples for all them, I dropped it very quickly, it is not sustainable, tools change over time forcing me to re-test and eventually adjust.
Giovanni
Nice project but I can see several reasons to not do that, let me explain my point.
Apparently that plugin focuses on managed build, I prefer to stick to makefiles because those are way easier to maintain. When I change a path or add a driver then I just have to change one .mk file and all projects are fine. Considering the number of projects part of ChibiOS this is not a small thing. Updating Keil and IAR projects is a PITA for this same reason (this is why there are few examples of those).
Project templates are nice but probably incompatible with ChibiOS because different startup, vectors and scatter files. This could confuse users, I would expect to start a new ChibiOS project using the templates but that would not be the case.
In general, if I start supporting one environment what about EM:Blocks, Atollic, Crossworks, CoIDE, Ride7 and all the others?
I prefer a neutral approach to development environments, however, nothing forbids installing the GNU ARM plugins on ChibiStudio or ChibiOS plugins on any other Eclipse-based environment. Initially I tried to provide examples for all them, I dropped it very quickly, it is not sustainable, tools change over time forcing me to re-test and eventually adjust.
Giovanni
-
tecnologic
- Posts: 124
- Joined: Tue Jan 10, 2012 8:42 am
- Has thanked: 21 times
- Been thanked: 5 times
Re: ChibiStudio and GNU ARM Eclipse Plugin
OK. I See the point with the makefiles. I use them too, because I misslike to mark nearly all chibios examples
And so on as exclude from build.
But the debug settings from the Plugin are very good.
Regards
Tec
And so on as exclude from build.
But the debug settings from the Plugin are very good.
Regards
Tec
- Giovanni
- Site Admin
- Posts: 14891
- Joined: Wed May 27, 2009 8:48 am
- Has thanked: 1202 times
- Been thanked: 996 times
Re: ChibiStudio and GNU ARM Eclipse Plugin
Maybe we should consider including parts of it by default. I suppose it is split in independent plugins.
Giovanni
Giovanni
-
tecnologic
- Posts: 124
- Joined: Tue Jan 10, 2012 8:42 am
- Has thanked: 21 times
- Been thanked: 5 times
Re: ChibiStudio and GNU ARM Eclipse Plugin
Yes, it is split in components.
Integration would be nice.
Integration would be nice.