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.
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
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.
cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
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