C/c++ indexer has encountered a problem eclipse .cproject file cocos2d-x version 3.3

cocos2d-x
#1

I am develop a new game using cocos2d-x version 3.3. First I complete game development in xcode and run it for iOS, It’s working fine.

When I import this project in eclipse first time it’s run correct. When we restart the eclipse I got “C/C++ indexer has encountered a problem” error from eclipse. I spend 4 hour for this issue and lastly I found solution.

When I look into .cproject file within proj.android folder I found every time extra configuration tag is adding in last.

	<cconfiguration id="0.1230402123.1377291156">
		<storageModule buildSystemId="org.eclipse.cdt.managedbuilder.core.configurationDataProvider" id="0.1230402123.1377291156" moduleId="org.eclipse.cdt.core.settings" name="Debug">
			<externalSettings/>
			<extensions>
				<extension id="org.eclipse.cdt.core.VCErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
				<extension id="org.eclipse.cdt.core.GmakeErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
				<extension id="org.eclipse.cdt.core.CWDLocator" point="org.eclipse.cdt.core.ErrorParser"/>
				<extension id="org.eclipse.cdt.core.GCCErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
				<extension id="org.eclipse.cdt.core.GASErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
				<extension id="org.eclipse.cdt.core.GLDErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
			</extensions>
		</storageModule>
		<storageModule moduleId="org.eclipse.cdt.core.externalSettings"/>
	</cconfiguration>

I removed this and app start working perfectly.I don’t know why It’s adding extra configuration every time but removing it work like charm.

Please look into this.

1 Like
Cocos 3.6 to compile android in eclipse
#2

Nah, don’t worry too much about eclipse complaining about c++, eclipse CDT is really buggy, Just ignore those C++ warnings in eclipse. use command line build build_native.py or cocos compile

I said this because I spent countless time on eclipse too for these warnings…

#3

Thanks, the same happened to me and I could fix it with your advise :wink: