[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[dsdp-dd-dev] RE: [cdt-dev] catchpoints
|
(bringing in the DD guys, who are essentially the same ;)
It doesn't really matter what project it is a part of. We need to make
sure DSF works nicely with the rest of the CDT and the best way to do
that is to think of it technically as part of the CDT.
For example, on the DSF/GDB/MI call today we discussed what the DSF
launch configs would look like. Going down that path as we are, though,
we're going to end up with two launch configurations that do the same
thing, just one for DSF and one for CDI. And the likelyhood that both
CDI and DSF are installed at the same time is going to be high as more
toolchains are supported on it. And that's going to be confusing.
Instead, we should be coming up with a common launch configuration
framework that supports both CDI and DSF for launch configurations they
have in common (i.e. local launches). And base it on the toolchain
concept that I would love to have added to the project model (i.e. the
toolchain selects the debugger too). Or something like that...
Doug.
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Elena Laskavaia
Sent: Tuesday, April 08, 2008 10:25 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] catchpoints
Sorry my mistake, I though it is part of dsdp project. Is is part of CDT
now?
Schaefer, Doug wrote:
>
> I'd prefer we start thinking of DSF as a part of the CDT. They == us.
> Which makes it a very good question.
>
> Doug.
>
>
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
