Merging launch framework

Andreas Pakulat apaku at gmx.de
Thu Apr 30 21:34:27 UTC 2009


On 28.04.09 00:36:32, Andreas Pakulat wrote:
> On 26.04.09 19:44:07, Andreas Pakulat wrote:
> > Hi,
> > 
> > good news, I've got the launch framework ready to execute applications and
> > also configure launches. That means I could merge now.
> > 
> > However, I've also had to disable gdb plugin basically (i.e. it doesn't
> > do anything at the moment) and I'm feeling kinda lost when trying to
> > find out how I can properly port it to the launch framework.
> > 
> > So I'd like some opinion on how we want to do the merging, should I just
> > merge what I have and we'll try to port gdb together. Or should I just
> > post a patch for current trunk (pretty huge diff however)?
> 
> Well, was actually easier than I thought after matching Niko's
> explanations (big thank you) with the actual code.
> 
> So, I've got a patch (sorry, too late to dive into git documentation to
> find out how to easily create a proper patch from a git branch, will do
> that tomorrow) that implements the run framework and allows to run and
> debug executables. Things that are missing
> 
> - support for project targets

I've fixed that now.

> - support for dependencies

I'll definetly fix that one tomorrow and also the smaller bugs that
still exist (actions for configs are not renamed when you rename the
config, auto-select of configs from projects doesn't work and sometimes
actions are not deleted from the submenu).

> - porting of gdbtest (I'm fearing this might be a bit more work)
> - porting of valgrind (shouldn't be too hard, but also a bit more work)
> - adds yet another "start debugger" action as I didn't understand how to
>   integrate with the existing one in debuggercontroller

The rest is up for adoption :) Not sure how much I can do this weekend.

Oh and yeah, I've comitted this stuff now, its been a royal pita with
keeping up with the changes from everybody and the new stuff does work in
general.

Andreas

-- 
Fine day for friends.
So-so day for you.




More information about the KDevelop-devel mailing list