Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » C / C++ IDE (CDT) » project error after migration from eclipse kepler to neon/and oxygen
project error after migration from eclipse kepler to neon/and oxygen [message #1771936] Fri, 01 September 2017 10:19
sancelot Mising name is currently offline sancelot Mising nameFriend
Messages: 4
Registered: November 2009
Junior Member
After migration from eclipse kepler to eclipse neon, some of my projects are emitting the following message .



Errors occurred during the build.
Errors running builder 'CDT Builder' on project 'API_SIMULATION'.
Internal error building project API_SIMULATION configuration Release
org.eclipse.cdt.managedbuilder.internal.core.ResourceConfiguration cannot be cast to org.eclipse.cdt.managedbuilder.core.IToolChain
Internal error building project API_SIMULATION configuration Release
org.eclipse.cdt.managedbuilder.internal.core.ResourceConfiguration cannot be cast to org.eclipse.cdt.managedbuilder.core.IToolChain

eclipse oxygen log:

java.lang.ClassCastException: org.eclipse.cdt.managedbuilder.internal.core.ResourceConfiguration cannot be cast to org.eclipse.cdt.managedbuilder.core.IToolChain
at org.eclipse.cdt.managedbuilder.internal.core.Tool.checkForMigrationSupport(Tool.java:3291)
at org.eclipse.cdt.managedbuilder.internal.core.Tool.resolveProjectReferences(Tool.java:983)
at org.eclipse.cdt.managedbuilder.internal.core.ResourceConfiguration.resolveProjectReferences(ResourceConfiguration.java:980)
at org.eclipse.cdt.managedbuilder.internal.core.Configuration.resolveProjectReferences(Configuration.java:2876)
at org.eclipse.cdt.managedbuilder.internal.core.Configuration.<init>(Configuration.java:433)
at org.eclipse.cdt.managedbuilder.internal.dataprovider.ConfigurationDataProvider.load(ConfigurationDataProvider.java:391)
at org.eclipse.cdt.managedbuilder.internal.dataprovider.ConfigurationDataProvider.loadConfiguration(ConfigurationDataProvider.java:557)
at org.eclipse.cdt.internal.core.settings.model.CConfigurationDescriptionCache.loadData(CConfigurationDescriptionCache.java:136)
at org.eclipse.cdt.internal.core.settings.model.CProjectDescription.loadDatas(CProjectDescription.java:196)
at org.eclipse.cdt.internal.core.settings.model.xml.XmlProjectDescriptionStorage.loadProjectDescription(XmlProjectDescriptionStorage.java:500)
at org.eclipse.cdt.internal.core.settings.model.xml.XmlProjectDescriptionStorage.getProjectDescription(XmlProjectDescriptionStorage.java:237)
at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.getProjectDescriptionInternal(CProjectDescriptionManager.java:426)
at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.getProjectDescription(CProjectDescriptionManager.java:408)
at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.getProjectDescription(CProjectDescriptionManager.java:402)
at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.getProjectDescription(CProjectDescriptionManager.java:395)
at org.eclipse.cdt.internal.core.model.CProject.computeSourceRoots(CProject.java:608)
at org.eclipse.cdt.internal.core.model.CProject.computeChildren(CProject.java:629)
at org.eclipse.cdt.internal.core.model.CProject.buildStructure(CProject.java:593)
at org.eclipse.cdt.internal.core.model.Openable.generateInfos(Openable.java:261)
at org.eclipse.cdt.internal.core.model.CElement.openWhenClosed(CElement.java:427)
at org.eclipse.cdt.internal.core.model.CElement.getElementInfo(CElement.java:305)
at org.eclipse.cdt.internal.core.model.CElement.getElementInfo(CElement.java:295)
at org.eclipse.cdt.internal.core.model.Parent.getChildren(Parent.java:55)
at org.eclipse.cdt.internal.core.model.CElement.accept(CElement.java:524)
at org.eclipse.cdt.internal.core.pdom.indexer.PDOMRebuildTask.createDelegate(PDOMRebuildTask.java:118)
at org.eclipse.cdt.internal.core.pdom.indexer.PDOMRebuildTask.run(PDOMRebuildTask.java:78)
at org.eclipse.cdt.internal.core.pdom.PDOMIndexerJob.run(PDOMIndexerJob.java:155)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)

I have some projects , which are static library.

Some executable are refering them in C/C++ / general/paths and symbols/project references tab.

(in which there are some configurations too)

I removed references in this tab and the mistake disappear.

This problem is very boring. Since you have to find which projects have problem and correct them.

Regards
S.Ancelot
Previous Topic:Eclipse is getting the wrong PATH path for C++, and is in the Java folder
Next Topic:GDB debug very slow with big variables
Goto Forum:
  


Current Time: Wed Apr 24 23:11:12 GMT 2024

Powered by FUDForum. Page generated in 0.03792 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top