[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Juno Aggregation Fails for Linux Tools due to missing TCF RSE
|
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Marc Khouzam
> Sent: Tuesday, October 11, 2011 4:22 PM
> To: 'CDT General developers list.'
> Cc: TCF Development (tcf-dev@xxxxxxxxxxx)
> Subject: Re: [cdt-dev] Juno Aggregation Fails for Linux Tools due to missing
> TCF RSE
>
> > -----Original Message-----
> > From: cdt-dev-bounces@xxxxxxxxxxx
> > [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Schaefer, Doug
> > Sent: Tuesday, October 11, 2011 4:14 PM
> > To: CDT General developers list.
> > Cc: TCF Development (tcf-dev@xxxxxxxxxxx)
> > Subject: Re: [cdt-dev] Juno Aggregation Fails for Linux Tools due to
> > missing TCF RSE
> >
> > Hi Jeff, this is actually probably a question for tcf-dev.
> >
> > There is a bit of history here. The TCF on the release train has only
> > been enough to satisfy the dependency for CDT's EDC debugger. RSE
> > wasn't part of that. So if it has been included in the past, it was by
> > accident.
> >
> > Now, that'll change for Juno
>
> So CDT will require RSE? I'm happy about this as it makes remote debug
> launches more user-friendly.
> I'm curious to know the motivation behind this dependency though. Sorry if I
> missed something said earlier.
Two points there. 1) I didn't say that, and 2) the CDT remote launch already depends on RSE.
The question is where do we put the TCF RSE plug-in on the release train, or any of TCF for that matter. Or maybe it just remains hidden so client plug-ins can satisfy their dependencies.
Doug
