Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Problem with 2019-09 M2

It looks like a JDT bug (or at least a change) to me. On 2019-06 everything is fine, but I get the same error as you in 2019-09 M2.

Would you like to create the JDT bug report, or should I?

In the meantime I think you should be fine with 2019-06 - there is a warning when you set the target platform to a newer version of Eclipse than you are developing with, but most of the time it is fine*


* I have only known one significant case in the last few years where developing target platform newer than dev version was a problem. At the time a new feature was added to junit plug-in tests and as a result you couldn't do junit plug-in test with the older dev platform. 

Jonah Graham
Kichwa Coders

On Fri, 9 Aug 2019 at 12:11, marco <marco.stornelli@xxxxxxxxx> wrote:
It doesn't seem a platform problem. Reverting commit "Bug 522200:
[C++17] Add support for structured binding declarations" it seems did
the trick. Now we need to understand what's the problem here. I guess
there's something wrong with the manifest change of org.eclipse.cdt.core.

Il 09/08/19 17:42, marco ha scritto:
> Hi,
> I'm now on 2019-09 M2. I setup everything again but when I try to
> compile CDT I see the error "ASTInclusionStatement class is alredy
> defined". This class is inside in project
> org.eclipse.cdt.core pacakge
> org.eclipse.cdt.internal.core.parser.scanner. Any tips?
> Thanks.
cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top