We have a project based on a slightly modified XULRunner that we are
building daily on Windows. When I bring it over to a Mac Pro (Intel), I
have the following problems.
Using the config file
mk_add_options MZBJDIR=@TPSRCDIR@//obj-app
ac_add_options
ac_add_options
ac_add_options
ac_add_options
ac_add_options
ac_add_options
ac_add_options
,venkman,inspector,editor/cascades
ac_add_options
mk_add_options MZ_CPRJECT=xulrunner
mk_add_options MZ_XUL_APP=1
I can build, but I expected to see in dist/bin a file like
XULRunnerDebug.app. I don't see it. I then try starting it from
terminal, say:
cd obj-app/dist/xpi-stage/app/
//bin/xulrunner-bin ./application.ini
In almost all cases it says that it can't read application.ini,
although the console is showing that chrome is getting loaded. At one
time, I saw the UI of our app, but the terminal window still had the
keyboard (and mouse, apparently) focus, so I couldn't do anything with
the app.
My question:
Is this building to completion, even though there is no .app file
(other than something called update.app)? If so, how should I be
starting it?
I also tried a universal build, by adding
$
to my mozconfig file. I get a ppc tree and an i386 tree, but neither
one goes to completion. The failure comes when it tries to find
something inside XULRunnerDebug.app, at a time when XULRunnerDebug.app
doesn't exist.
Can anybody give me some hints or pointers?
dev-builds mailing list
dev-builds (AT) lists (DOT) mozilla.org

I think I pushed "Post message" twice.
I should have said that we started with XULRunner code from about July
20 (version 1.9a1).
dev-builds mailing list
dev-builds (AT) lists (DOT) mozilla.org

When I run "xulrunner-bin " I got some errors, so I
installed XULRunner 1.8.0.4. With that in /Library/Frameworks, I built
the 'simple' example and tried:
/
<path/to/application.ini>
It came back with no errors. I expected to find "Simple.app" in
/Applications/MozillaTest (the vendor according to the application.ini
file), yet there seems to be no Simple.app on my disk.

Running just
/
<path/to/application.ini>
does display the Simple app (without keyboard or mouse focus), so I
know that I got the path to the application.ini file right.

I built an App.app folder using the layout given on

Running the perl script does start XULRunner and it finds the
application.ini file, but it doesn't seem to find the chrome (I did
this with Xulrunner 1.9a1). And the Mac, not surprisingly, doesn't
recognize my App.app as an application.

dev-builds mailing list
dev-builds (AT) lists (DOT) mozilla.org

Barry wrote:
When I run "xulrunner-bin " I got some errors, so I
installed XULRunner 1.8.0.4. With that in /Library/Frameworks, I built
the 'simple' example and tried:
/
<path/to/application.ini>

Please read the docs closer ;-) you shouldn't pass the path
to application.ini. You pass it the path to your zipped .xulapp.
Alternatively, though this is not really documented, you can pass it the
path to an unzipped *directory*.

It came back with no errors. I expected to find "Simple.app" in
/Applications/MozillaTest (the vendor according to the application.ini
file), yet there seems to be no Simple.app on my disk.

It's a known issue that the flag doesn't provide useful error
reporting when it fails. I intend to work on that.v

dev-builds mailing list
dev-builds (AT) lists (DOT) mozilla.org

Thanks, Ben.

The last part of the path parameter is scrolled out of the window,
which is probably why I missed it.

I passed it an unzipped directory, and it is now working.

Thanks again.

Benjamin Smedberg wrote:
Barry wrote:
When I run "xulrunner-bin " I got some errors, so I
installed XULRunner 1.8.0.4. With that in /Library/Frameworks, I built
the 'simple' example and tried:
/
<path/to/application.ini>

Please read the docs closer ;-) you shouldn't pass the path
to application.ini. You pass it the path to your zipped .xulapp.
Alternatively, though this is not really documented, you can pass it the
path to an unzipped *directory*.

It came back with no errors. I expected to find "Simple.app" in
/Applications/MozillaTest (the vendor according to the application.ini
file), yet there seems to be no Simple.app on my disk.

It's a known issue that the flag doesn't provide useful error
reporting when it fails. I intend to work on that.v

dev-builds mailing list
dev-builds (AT) lists (DOT) mozilla.org