Re: [cdt-dev] Dropping 32-bit support and building against latest platfo

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

I agree, lets not worry about older platform versions. 

AFAIK so far, we have just not been updating platform version with each new release of the platform due to the overhead required and doing so requires CDT contributors to be using at least that platform version to develop CDT with. We have updated platform version as needed, such as when CDT wants access to new features in platform.

Jonah

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

On Mon, 11 Mar 2019 at 10:31, Doug Schaefer <dschaefer@xxxxxxxxxxxxxx> wrote:

+1

I've never been a fan of expending community resources maintaining compatibility with old platform releases. If vendors need that for a product, they should be responsible for that. We need to make sure the community is successful and manage the brand of CDT and the C/C++ IDE is the main vehicle for that.

Thanks!

Doug.

On Mon, 2019-03-11 at 13:28 +0000, William Riley wrote:

Hi Marc-Andre, Jonah

 

I was about to start looking at this myself, as the 4.8 platform is incompatible with the GTK version in the standard pod templates on the new Jenkins system.

 

Seems to make sense to move. We could always add extra jobs/pipeline steps to run the tests against multiple platform versions, even if the default is 4.11.

 

Regards
William

 

From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> On Behalf Of Jonah Graham
Sent: 11 March 2019 13:17
To: CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Dropping 32-bit support and building against latest platform

 

Hi Marc-Andre,

 

That would be great.

 

Jonah 

 

On Sat, 9 Mar 2019, 00:50 Marc-Andre Laperle, <malaperle@xxxxxxxxx> wrote:

Hi,

 

You might have noticed that CDT doesn’t build against the latest platform (4.11) when built from Maven/Tycho, it gives an error like:

"The type org.eclipse.swt.widgets.Shell cannot be resolved. It is indirectly referenced from required .class files”

 

It is actually caused by unsupported target environments configuration which causes SWT to not be found. Eclipse Platform 4.10 removed support for 32-bit environments but CDT still builds against them by using Platform 4.8. The downside to this is that tests are not being ran against 4.11 and the stand-alone debugger is still based on Platform 4.8. Those are not show-stoppers but not ideal for future releases.

 

So, I suggest removing 32-bit support for the next CDT version, coinciding with Eclipse 2019-06.

 

Unless there is any objection, I will prepare a commit for the master branch to remove relevant plugins, remove the target environments in the config and update the target platform to 4.11.

 

Cheers,

Marc-André

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev

Renesas Electronics Europe GmbH,Geschaeftsfuehrer/President : Michael Hannawald, Sitz der Gesellschaft/Registered office: Duesseldorf, Arcadiastrasse 10, 40472 Duesseldorf, Germany,Handelsregister/Commercial Register: Duesseldorf, HRB 3708 USt-IDNr./Tax identification no.: DE 119353406 WEEE-Reg.-Nr./WEEE reg. no.: DE 14978647

_______________________________________________

cdt-dev mailing list

cdt-dev@xxxxxxxxxxx

To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://urldefense.proofpoint.com/v2/url?u=https-3A__www.eclipse.org_mailman_listinfo_cdt-2Ddev&d=DwICAg&c=yzoHOc_ZK-sxl-kfGNSEvlJYanssXN3q-lhj0sp26wE&r=NrrbvTHWa2Nbp_kAN0Hl1o3lM1WAwSes64uBjxjNhMc&m=7hB4HbOc6mvcu-HEJXAZOSDrlS5fm-v36uWxQ_4jNCI&s=4YNM9BS5g-6GGY2vaRNrS8x8XELXKsyvOgptRQyPkAU&e=

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev