[cdt-dev] Preventing Eclipse/CDT from offering to debug embedded code lo

[Branko Drevenšek <branko.drevensek@xxxxxxxxx>]

Hi.

I'm integrating our gcc based toolchain with Eclipse/CDT.
One thing that bothers me and will probably confuse users is the fact, 
that when user tries to run embedded application for the first time by 
clicking on run or debug icons, Eclipse asks whether to debug 
application as "Local C/C++ application" or "'our' embedded application" 
(as defined in launch shortcut).

Application will certainly not run as local c/c++ application using 
system default gdb... Is there an easy way to prevent this dialog from 
popping up? I've read through code that does this and it mostly checks 
for project natures, and since we keep C/C++ nature and add our own...
TargetPlatform element has osList&archList fields which are supposed to 
do something, but anything I put there makes no difference (didn't 
really expect it to, since our launcher doesn't tell, it can launch 
that). We use DSF launch derived from cdt.debug.gdbjtag.
---
Now on that. I have another question.
In there, there is GDBJtagDSFFinalLaunchSequence class. It's based on 
cdt.dsf.gdb.launching.FinalLaunchSequence, which has recently been 
modified to extend ReflectionSequence to allow easier extension. As 
GDBJtagDSFFinalLaunchSequence extends "simple" Sequence, i had to copy 
most of it's code to adapt it to our requirements. I would expect that 
GDBJtagDSFFinalLaunchSequence would be extended more often than 
FinalLaunchSequence.

As far as I understand it, to contribute to CDT one has to raise a bug 
and provide a patch, which basically needs to be less than 250 LOC. I 
would do this (GDBJtagDSFFinalLaunchSequence based on 
ReflectionSequence), but I guess refactoring whole thing to extend 
ReflectionSequence would create larger patch. Is there anything I can to 
about it?

Thanks in advance.

Branko