Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] [tcf-dev] CDI is now removed for CDT 9.0

Hi Jonah, Doug, all –

 

I’m perfectly fine with option 2 (pulling a copy of the single CDT 9 API method that we need into TCF).

In fact we have already merged the contribution, and I have re-enabled the TCF C/C++ Launcher for

Our Simrel Neon M6 contribution.

 

Many thanks, especially to Jonah, for the quick action and helping out with a code contribution !!!

 

Thanks,

Martin

--

Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River

direct +43.662.457915.85  fax +43.662.457915.6

 

From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: Sunday, March 13, 2016 6:19 PM
To: CDT General developers list.
Cc: TCF Development
Subject: Re: [tcf-dev] [cdt-dev] CDI is now removed for CDT 9.0

 

Oops. Sending again as I forgot I had unsubscribed from tcf-dev.

 

On Sun, Mar 13, 2016 at 1:15 PM, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote:

On Sun, Mar 13, 2016 at 11:44 AM, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:

> While I was there I found an upcoming API incompatibility error because
> of some other (unrelated to CDI removal) API change. I have raised a
> bug and provided a fix. See http://eclip.se/489489 and its associated
> gerrit https://git.eclipse.org/r/68276 Note this won't build until your
> target platform is updated for a more recent CDT build.

Martin has -2'ed this because "We need TCF to be compatible with both
CDT 9.0 and 8.x from a single source. Can you propose a solution
making that possible ?"

I have proposed a solution (2 mutually exclusive ones actually), see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=456116#c9

However I want to raise as an issue that I am not sure how reasonable
it is and what the CDT API consumers expectation should be regarding
using a single source for CDT 8.8 and CDT 9. Because of the inherent
problem of maintaining API compatibility with CDT 8.x when doing CDT
9.0, My recommendation is that the second option from my comment above
be adopted by TCF.

 

+1 for option 2. I've done that in the past with Momentics and it worked well enough. If you're faced with supporting two major versions of a dependency you end up cloning or forking to make that work. But I feel sad for teams that have such a requirement.

 

Removing CDI broke the Momentics build, but Elena worked on Friday to migrate our last remaining functionality that depended on it. I expect others to do the same whether now or sometime after the CDT 9.0 release as their business warrants.

 

We gave months of warning that we were removing CDI. And we are making sure to get it done by M5 to give adopters a last chance time to react and adjust their code. I guess for TCF, it's that time.

 

Doug.

 


Please let me know if I have understood the issues properly or not.

Thanks
Jonah


~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com

On 12 March 2016 at 20:19, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
>
> Hi Martin,
>
> I have submitted a couple of gerrits to fix the issue as far as I can tell.
>
> TCF still had dependency on org.eclipse.cdt.debug.mi.{core,ui} but TCF was not actually using them, so I updated manifests, features, etc. See http://eclip.se/489483 and its associated gerrit https://git.eclipse.org/r/68277
>
> While I was there I found an upcoming API incompatibility error because of some other (unrelated to CDI removal) API change. I have raised a bug and provided a fix. See http://eclip.se/489489 and its associated gerrit https://git.eclipse.org/r/68276 Note this won't build until your target platform is updated for a more recent CDT build.
>
> I trust I have addressed your issues. Please let me know if there is anything I can help in with the transition away from CDI.
>
> Jonah
>
>
>
> ~~~
> Jonah Graham
> Kichwa Coders Ltd.
> www.kichwacoders.com
>
> On 12 March 2016 at 13:58, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
>>
>> Hi Martin,
>>
>> I will have a look at TCF this weekend and see if I can make a suggestion. I am not familiar with TCF, so perhaps I can come back to you (via this list) with follow ups?
>>
>> Thanks
>> Jonah
>>
>>
>>
>>
>> ~~~
>> Jonah Graham
>> Kichwa Coders Ltd.
>> www.kichwacoders.com
>>
>> On 12 March 2016 at 11:18, Oberhuber, Martin <Martin.Oberhuber@xxxxxxxxxxxxx> wrote:
>>>
>>> Hi all,
>>>
>>>
>>>
>>> Turned out that the TCF Project’s “C/C++ Remote Debug (over TCF/TE) Launch” used CDI:
>>>
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=489483
>>>
>>>
>>>
>>> We’d appreciate your help and suggestions how to resolve this.
>>>
>>>
>>>
>>> Essentially, this Launcher uses TCF/TE for bootstrapping (download the exe, launch gdbserver).
>>>
>>> Since CDT now offers org.eclipse.remote for these services, and TCF/TE offers an o.e.remote
>>>
>>> Filesystem implementation, there is a potential chance going that route; but it is possible that
>>>
>>> some features of TCF/TE are lost that way.
>>>
>>>
>>>
>>> Keeping the launcher, and using DSF instead of CDI is obviously the other option. Are there any
>>>
>>> Migration docs? Could you assist us with migration based on your experience so far ?
>>>
>>>
>>>
>>> Many thanks !
>>>
>>> Martin
>>>
>>> --
>>>
>>> Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River
>>>
>>> direct +43.662.457915.85  fax +43.662.457915.6
>>>
>>>
>>>
>>> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
>>> Sent: Wednesday, March 09, 2016 5:43 PM
>>> To: CDT General developers list.
>>> Subject: [cdt-dev] CDI is now removed for CDT 9.0
>>>
>>>
>>>
>>> Hey gang,
>>>
>>> Thanks to the hard work of Jonah and the thorough review with Marc, the CDI debug framework has now been removed for CDT 9.0.
>>>
>>> This is something we talked about for a long time as our focus switched solely to DSF and CDI was left unmaintained. CDI got us on a great start, but we really don't have enough contributions to keep both going.
>>>
>>> Please test out against CDT master and let us know if we over deleted anything.
>>>
>>> Doug.
>>>
>>>
>>> _______________________________________________
>>> cdt-dev mailing list
>>> cdt-dev@xxxxxxxxxxx
>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>
>>
>
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev

 

 


Back to the top