AVR Support as GSoC

Julian Bäume julian at svg4all.de
Thu Mar 25 23:59:21 UTC 2010

On Tuesday 23 March 2010 22:50:41 Amilcar do Carmo Lucas wrote:
> On Tuesday 23 March 2010 22:38:50 Jonathan Schmidt-Dominé - Developer wrote:
> > You would have to develop some plugins providing certain features for
> > micro- controllers, please describe what these plugins should do. I guess
> > it should be more than invoking the build-system with some special flags.
> I think KTechLab already does some of this.
> Maybe the correct way to do it is to port ktechlab to kdevplatform ?
You are partly right. At the moment, we are working hard to port KTechLab to 
KDevPlatform. Basic functionality is already there, but support for different 
MCUs is still on our TODO-list. I'd be fine if this would be implemented in 
KDevelop, because we would directly benefit from this ;D

What I would like to see is some consistent GUI for the different MCUs out 
there. In KTechLab, we had (it's not ported to KDE4, yet) support for the sdcc 
(http://sdcc.sf.net). Only the simulation part is limited to PIC, for now. But 
the toolchain part could be extended to provide the complete set of sdcc-
supported hardware. Providing a development platform for different MCUs is one 
of the goals of KTechLab. That's why we are porting everything to KDevPlatform 
at the moment. Providing support for the different toolchains out there would 
be cool but this isn't directly related to KTechLab. So after we ported our 
PIC support to KDevPlatform, it can easily be moved into some other project. I 
would really like to see the plain debugging and toolchain plugins to be 
developed outside KTechLab, so we can concentrate on what we want to do best: 
visualize the debugging information and use this data to simulate the MCUs 
within a circuit. But since there is no place for these plugins to go, at the 
moment, I'd rather maintain them in the KTechLab sources than nowhere at all.

bye then

More information about the KDevelop-devel mailing list