Merging launch framework

[Andreas Pakulat]

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
- support for dependencies
- 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

So my plan now is that as soon as I've got a diff ready I'll post it and
fix up the first two things (which should be easy). If (after reading
the patch of course) nobody objects I'm going to merge this stuff to
trunk in a few days (probably saturday as I won't have network on
friday) and then we can finish up the other 3 points.

Andreas

-- 
Don't tell any big lies today.  Small ones can be just as effective.