Hi Marc,
Just to reiterate what you mean, DSF is depended
on CDT and it is part of the CDT installation.
There is a hand full of dependency on CDT,
i.e IAddress, Addr64, ICBreakpoint, ICBreakpointExtension,
CSourceLookupDirectory, CDebugImages. Can these interfaces and implementations
be redefined in DSF and the implementation be re-implemented in DSF? So that DSF
can remove the CDT dependency for the debugging part.
While I am debugging DSF code for setting
a CLineBreakpoint, CDIDebugModel was sucked in for the breakpoint marker, as
well as the CDebugModemPresentation. It looks like DSF is depended in CDT in a
number of areas.
I am trying to make sense of the
relationship between DSF and CDT. Are there any reasons why DSF is relying on
some of the CDT interfaces and implementation?
Thanks again,
Patrick
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Marc Khouzam
Sent: Tuesday, April 21, 2009
11:57 AM
To: CDT General developers list.
Subject: RE: [cdt-dev] DSF
depended on CDT
Hi,
DSF and DSF-GDB have now been moved to the
CDT project.
What that means is that, starting with
Galileo (eclipse 3.5) when installing CDT you will automatically
get DSF and DSF-GDB.
There are no other dependencies.
Marc
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Chuong, Patrick
Sent: Tuesday, April 21, 2009
11:08 AM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] DSF depended on
CDT
Hi,
I am browsing through the DSF plugins and I see that DSF
depended on several CDT plugins, is this a temporary solution? Will this
dependency goes away in future DSF release? Is there any other runtime
dependency that you can point out that is not explicitly defined in the plugin
manifest file?
Thanks,
Patrick
