Difference between revisions of "XULRunner 1.8"
(→Mac OS) |
(→Linux) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
+ ... chrome which is part of the application | + ... chrome which is part of the application | ||
* ... additional application files such as icons, etc | * ... additional application files such as icons, etc | ||
| − | * myapplicationname.exe (This is the "stub executable"... you should copy and rename this file from xulrunner-stub.exe in your XULRunner installation.) | + | * myapplicationname.exe (This is the "stub executable"... you should copy and rename this |
| + | file from xulrunner-stub.exe in your XULRunner installation.) | ||
* xulrunner/ | * xulrunner/ | ||
+ ... copy xulrunner/ to this directory | + ... copy xulrunner/ to this directory | ||
| + | |||
=== Mac OS === | === Mac OS === | ||
| Line 22: | Line 24: | ||
+ Frameworks/ | + Frameworks/ | ||
# XUL.framework/ | # XUL.framework/ | ||
| − | * files copied from /Library/Frameworks/XUL.framework/Versions/1.8/... | + | * files copied from /Library/Frameworks/XUL.framework/Versions/1.8/... |
| − | sure you copy all symlinks correctly | + | make sure you copy all symlinks correctly |
(use rsync -rl /Library/Frameworks/XUL.framework ...). | (use rsync -rl /Library/Frameworks/XUL.framework ...). | ||
+ Resources | + Resources | ||
| Line 36: | Line 38: | ||
# xulrunner (This is the "stub executable"... you should copy this file from | # xulrunner (This is the "stub executable"... you should copy this file from | ||
/Library/Frameworks/XUL.framework/Versions/1.8/xulrunner. | /Library/Frameworks/XUL.framework/Versions/1.8/xulrunner. | ||
| + | |||
=== Linux === | === Linux === | ||
| − | + | ||
Most Linux applications are distributed as simple .tar.bz2 archives which can be unpacked by the user wherever they wish. The archive should be structured as follows: | Most Linux applications are distributed as simple .tar.bz2 archives which can be unpacked by the user wherever they wish. The archive should be structured as follows: | ||
| Line 48: | Line 51: | ||
+ ... chrome which is part of the application | + ... chrome which is part of the application | ||
o ... additional application files such as icons, etc | o ... additional application files such as icons, etc | ||
| − | o myapplicationname (This is the "stub executable"... you should copy and rename this file from xulrunner-stub in your XULRunner installation.) | + | o myapplicationname (This is the "stub executable"... you should copy and rename this file |
| + | from xulrunner-stub in your XULRunner installation.) | ||
o xulrunner/ | o xulrunner/ | ||
+ ... copy xulrunner/ to this directory | + ... copy xulrunner/ to this directory | ||
Latest revision as of 12:35, 25 November 2006
Deploying XULRunner 1.8
Windows
If you do not wish to use the XUL Runner installer, the installed files should be arranged in the following directory structure:
* installdir/
* application.ini
* components/
+ ... components which are part of the application
* chrome/
+ ... chrome which is part of the application
* ... additional application files such as icons, etc
* myapplicationname.exe (This is the "stub executable"... you should copy and rename this
file from xulrunner-stub.exe in your XULRunner installation.)
* xulrunner/
+ ... copy xulrunner/ to this directory
Mac OS
On Mac OS X, the XULRunner framework bundle is placed in your application bundle:
* MyApp.app/
o Contents/
+ Info.plist
+ Frameworks/
# XUL.framework/
* files copied from /Library/Frameworks/XUL.framework/Versions/1.8/...
make sure you copy all symlinks correctly
(use rsync -rl /Library/Frameworks/XUL.framework ...).
+ Resources
# application.ini
# app_icon.icns
# components/
* ... components which are part of the application
# chrome/
* ... chrome which is part of the application
# ... additional application files such as icons, etc
+ MacOS/
# xulrunner (This is the "stub executable"... you should copy this file from
/Library/Frameworks/XUL.framework/Versions/1.8/xulrunner.
Linux
Most Linux applications are distributed as simple .tar.bz2 archives which can be unpacked by the user wherever they wish. The archive should be structured as follows:
* appname/
o application.ini
o components/
+ ... components which are part of the application
o chrome/
+ ... chrome which is part of the application
o ... additional application files such as icons, etc
o myapplicationname (This is the "stub executable"... you should copy and rename this file
from xulrunner-stub in your XULRunner installation.)
o xulrunner/
+ ... copy xulrunner/ to this directory
