Eclipse Community Forums: C / C++ IDE (CDT) » Problems with headlessbuild Win7 64bit, Indigo CDT 8, Java7

Home » Language IDEs » C / C++ IDE (CDT) » Problems with headlessbuild Win7 64bit, Indigo CDT 8, Java7

Problems with headlessbuild Win7 64bit, Indigo CDT 8, Java7 [message #766386]

Thu, 15 December 2011 12:17

Eclipse User

Dear all,

We have got a project using Eclipse CDT managed build (not make).

In our previous setup (Win XP, Galileo) everything worked fine:
C:\Programme\eclipse_cdt\eclipse.exe -nosplash -verbose > build.tmp -application org.eclipse.cdt.managedbuilder.core.headlessbuild -data Gen_MU\Targetcode -cleanBuild 16FX32x_

We've migrated to Win 7. We installed the latest eclipse (Indigo, CDT 8 ) and are using Java 7.

The project can be built in eclipse. But using the healessbuild a window pops up telling me that "Java was started but returned exit code=1" (see attached printscreen).

I think we have got a problem with Java 32 vs. 64 bit. I've already tried to
- set the -vm path in eclipse.ini to several different java installations
- set the -vm path as argument to the above command line
- set the environment variable JAVA_HOME
- set -XX:-UseCompressedOops in eclipse.ini (no idea what it does but read in a forum)

everything without any success.

What is wrong with my setup?

Thank you

Attachment: eclipse_java_error.jpg
(Size: 98.94KB, Downloaded 422 times)

Re: Problems with headlessbuild Win7 64bit, Indigo CDT 8, Java7 [message #768439 is a reply to message #766386]

Tue, 20 December 2011 01:41

Eclipse User

It seems that my description of the problem is not specific enough. What other information should I provide?

Is there someone who has headlessbuild working under Win7 64bit?

Thanks

Re: Problems with headlessbuild Win7 64bit, Indigo CDT 8, Java7 [message #768480 is a reply to message #768439]

Tue, 20 December 2011 03:24

Eclipse User

You should look at the log file in MY_WORKSPACE/.metadata/.log. Perhaps you get more info then.

Re: Problems with headlessbuild Win7 64bit, Indigo CDT 8, Java7 [message #768531 is a reply to message #768480]

Tue, 20 December 2011 05:22

Eclipse User

Well, that seems to me that I don't have a java problem but a problem with the Fujitsu plugin.
Do you interpret it the same? I guess I should contact the developer of that plugin.

!SESSION 2011-12-20 10:56:22.714 -----------------------------------------------
eclipse.buildId=M20110909-1335
java.version=1.7.0_02
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE
Framework arguments: -product org.eclipse.epp.package.cpp.product -verbose -application org.eclipse.cdt.managedbuilder.core.headlessbuild -cleanBuild 16FX32x_
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.cpp.product -verbose -application org.eclipse.cdt.managedbuilder.core.headlessbuild -data Gen_MU\Targetcode -cleanBuild 16FX32x_

!ENTRY org.eclipse.cdt.managedbuilder.core 4 0 2011-12-20 10:56:25.216
!MESSAGE Orphaned CDT build configuration [org.eclipse.cdt.fujitsuF2MC16.exe.target.win32.MB96F326RSA.release.1533483269]: parent extension cfg [org.eclipse.cdt.fujitsuF2MC16.exe.target.win32.MB96F326RSA.release] not found
!STACK 0
java.lang.Exception
at org.eclipse.cdt.managedbuilder.core.ManagedBuilderCorePlugin.error(ManagedBuilderCorePlugin.java:226)
at org.eclipse.cdt.managedbuilder.internal.core.Configuration.loadFromProject(Configuration.java:852)
at org.eclipse.cdt.managedbuilder.internal.core.Configuration.<init>(Configuration.java:400)
at org.eclipse.cdt.managedbuilder.internal.dataprovider.ConfigurationDataProvider.load(ConfigurationDataProvider.java:366)
at org.eclipse.cdt.managedbuilder.internal.dataprovider.ConfigurationDataProvider.loadConfiguration(ConfigurationDataProvider.java:541)
at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.loadData(CProjectDescriptionManager.java:1115)
at org.eclipse.cdt.internal.core.settings.model.CConfigurationDescriptionCache.loadData(CConfigurationDescriptionCache.java:95)
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:486)
at org.eclipse.cdt.internal.core.settings.model.xml.XmlProjectDescriptionStorage.getProjectDescription(XmlProjectDescriptionStorage.java:231)
at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.getProjectDescriptionInternal(CProjectDescriptionManager.java:416)
at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.getProjectDescription(CProjectDescriptionManager.java:398)
at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.getProjectDescription(CProjectDescriptionManager.java:393)
at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.getProjectDescription(CProjectDescriptionManager.java:386)
at org.eclipse.cdt.internal.core.model.CProject.computeSourceRoots(CProject.java:603)
at org.eclipse.cdt.internal.core.model.CProject.computeChildren(CProject.java:624)
at org.eclipse.cdt.internal.core.model.CProject.buildStructure(CProject.java:588)
at org.eclipse.cdt.internal.core.model.Openable.generateInfos(Openable.java:265)
at org.eclipse.cdt.internal.core.model.CElement.openWhenClosed(CElement.java:428)
at org.eclipse.cdt.internal.core.model.CElement.getElementInfo(CElement.java:307)
at org.eclipse.cdt.internal.core.model.CElement.getElementInfo(CElement.java:297)
at org.eclipse.cdt.internal.core.model.Parent.getChildren(Parent.java:55)
at org.eclipse.cdt.internal.core.model.CElement.accept(CElement.java:527)
at org.eclipse.cdt.internal.core.pdom.indexer.PDOMUpdateTask.createDelegate(PDOMUpdateTask.java:95)
at org.eclipse.cdt.internal.core.pdom.indexer.PDOMUpdateTask.run(PDOMUpdateTask.java:78)
at org.eclipse.cdt.internal.core.pdom.PDOMIndexerJob.run(PDOMIndexerJob.java:137)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Re: Problems with headlessbuild Win7 64bit, Indigo CDT 8, Java7 [message #768734 is a reply to message #768531]

Tue, 20 December 2011 12:16

Eclipse User

Quote:

Well, that seems to me that I don't have a java problem but a problem with the Fujitsu plugin.
Do you interpret it the same? I guess I should contact the developer of that plugin.

Yep. Seems to be a problem with this plugin (does not support Java 7 or x64 or is not compatible to Indigo).

Previous Topic:	Debug view freezes
Next Topic:	What is the output file extension for builds (Indigo running on a MAC)?

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Jun 16 03:57:25 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter