[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [cdt-dev] Renaming "DSF Disassembly"
|
Why are there dependencies on gdb specific plugins for the
generic disassembly view? Shouldn't those plugins only contain gdb
specifics? We don't typically bundle any gnu specific parts of CDT with
our products since we don't use any gnu tools. That's the reason they're
in separate plugins afterall.
As far as the view being in DSF vs CDT core, it doesn't
matter that much to me since we'll be shipping a DSF debugger. Our
existing products based on CDT 6.0 only have a CDI debugger and we do no bundle
DSF with those. I'm not sure if any vendors will have that scenario with
CDT 7.0.
For viewer to work with CDI there're the following
dependencies:
1. /org.eclipse.cdt.dsf.ui - the actual DSF viewer and
its dependencies org.eclipse.cdt.dsf,
org.eclipse.cdt.dsf.gdb
2. org.eclipse.cdt.dsf.gdb.ui - for IToggleBreakpointsTargetExtension and IMoveToLineTarget/ IResumeAtLineTarget / IRunToLineTarget
adapters
Teo
Given
the view is still in DSF, why would we move the prefs out of the DSP
plugin?
Well, if it's shared between DSF and CDI, then it's really not a
DSF feature and I would assume it would be in org.eclipse.cdt.debug.ui.
Is DSF required in CDT 7.0 or can vendors ship without it if they're only
using CDI?