From my very recent (like 3 minutes ago)
understanding of the use of features, I gather that we want to provide
features that integrators will not have
to remove plugins from (originally, I
thought integrators would just remove the org.eclipse.dd.gdb.launch jar
file, if there
were not interested in it.)
If that is our goal, then your suggestion
below makes a lot of sense. My only concern is the naming of the
features:
having DSF-MI contain all our GDB code, and
GDB-MI just the ability to launch it, does not seem obvious to me.
But I wonder how the features to indicate
that there is GDB -code- and GDB -launching-....
Is it easy to rename features?
Marc
I'm starting to second guess our features in general. Currently we
have:
- Traditional Memory Rendering
- IPXACT Editor & Checker
- DSF SDK
- This includes both DSF and MI components
- GDB-MI Implementation (Requires DSF SDK)
- This includes the GDB component only
The problem is that if someone wants to use DSF with a non-MI based
debugger, they still have to include the MI component from the DSF-SDK
feature. I suggest that we crate a new feature: DSF-MI and include
both MI and GDB plugins in it. Then we can modify the GDB-MI feature
to only contain the GDB launch registration. For commercial debuggers
that use the MI protocol, it shouldn't be a big burden to include the
gdb and gdb.ui plugins, since they are rather light.
Opinions?
-Pawel
