On Linux build, packaging .crx requires an X display to be present

[GoogleCodeExporter]

Yet another drawback of using the Chrome executable to package the 
speedtracer.crx is that on Linux, aside from having to specify chrome.path 
on the ant command line, you must have an X display running.  This is kind
of a pain in a continuous build environment (or like me building remotely)

build:
     [exec]
     [exec] (chrome:7433): Gtk-WARNING **: cannot open display:
     [exec] Result: 1

BUILD FAILED
/home/zundel/SpeedTracer/src/build.xml:40: The following error occurred 
while executing this line:
/home/zundel/SpeedTracer/src/client/build.xml:74: speedtracer.crx was not 
produced.

A workaround is to run Xvfb to create a virtual X display.

Original issue reported on code.google.com by zundel@google.com on 19 Dec 2009 at 1:46

[GoogleCodeExporter]

We could also build the crx without using the Chrome executable. The format is 
pretty 
simple. I know thee are ruby & python scripts out there to do it already.

Original comment by knor...@google.com on 25 Jan 2010 at 3:59

[GoogleCodeExporter]

Is this a closed issue?

Original comment by sarahgsm...@google.com on 4 Aug 2011 at 12:50

[GoogleCodeExporter]

We worked through this in the continuous build machine.

Original comment by zundel@google.com on 4 Aug 2011 at 2:14

• Changed state: Done