Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: Headless build [was Re: [cdt-dev] RIP Wascana, Build System]

That UI-Error is exactly the problem with CDT headless builds. The variables framework used for build variables like resource_loc, is trying to invoke something in the UI layer.


On Mon, May 25, 2009 at 4:31 AM, Kaestel-Baumgartner Harald (DCC/EDF2) <Harald.Kaestel-Baumgartner@xxxxxxxxxxxxxxx> wrote:

> From: James Blackburn <jamesblackburn@xxxxxxxxx>
> > 2009/5/22 Elena Laskavaia <elaskavaia@xxxxxxx>:
> > Implementing headless builder from CDT is pretty straight
> > forward. It is
> > like 100 lines of code
> Indeed, that's been my experience, though I haven't before now needed
> to implement my own IApplication target instead using the one provided
> by the platform as worked fine:

For us the headless build (for managed projects) works without the jdt_apt_building (avoids jdt dependencies in cdt).
org.eclipse.ant.core.antRunner and a simple build-script is enough. The command looks like this:
...\eclipse.exe -data <path to Workspace> -console -noSplash -application  org.eclipse.ant.core.antRunner -buildfile build.xml -logfile build.log -vmargs -Dorg.eclipse.cdt.core.console=org.eclipse.cdt.core.systemConsole

There is a UI-Error in the .log-File that could be solved (cdt
!ENTRY org.eclipse.osgi 4 0 2009-05-25 09:20:09.119
!MESSAGE An error occurred while automatically activating bundle org.eclipse.debug.ui (75).
org.osgi.framework.BundleException: Exception in org.eclipse.debug.internal.ui.DebugUIPlugin.start() of bundle org.eclipse.debug.ui.
       at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(
Root exception:
       at org.eclipse.debug.internal.ui.DebugUIPreferenceInitializer.setDefault(

Just my 2 cent ;)

cdt-dev mailing list

Back to the top