[cdt-debug-dev] CDT, RCP & my intentions

[Øyvind Harboe <oyvind.harboe@xxxxxxxxx>]

There has been lots of postings on the mailing list with stuff relevant
to my CDT RCP excursion. It will take a while for me to digest all the
suggestions & pointers.

I believe the GDB GUI based on CDT & RCP can achieve a couple of things:

- help enumerate outstanding issues, e.g. CDT has a false dependency
  on org.eclipse.team.core(reported and fixed, but not committed).
- from the Zylin Embedded CDT there is plenty of evidence that CDT
  basically works as a GDB GUI, so perhaps I'll find some way to hack
  around the remainig problems. My CDT hacks have a way of evolving into
  something that is eventually committed to CDT CVS. (Sometimes it takes
  a year or two, which is fine :-) The first problem I'll try to tackle
  is projectless debugging. Ideally I'd like to have an EmptyProject
  class, but perhaps I'll just ship the whole thing w/workspace that
  contains a "Dummy" project and then default to that dummy project.
- I do not intend to fix all the problems I find, but if this works
  out well, I do intend to regularly compile the GDB GUI from CDT CVS,
  add and remove hacks(as CDT CVS makes the hacks obsolete)
  and publish binaries to collect comments & feedback.
- As always I test against ARM JTAG and one or two other embedded
  CPU's.

-- 
Øyvind Harboe
http://www.zylin.com