Difference between revisions of "How to deploy XULRunner"

From CDOT Wiki
Jump to: navigation, search
 
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Windows ==
+
== 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:
 
If you  do not wish to use the XUL Runner installer, the installed files should be arranged in the following directory structure:
  
Line 9: 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
 +
 +
=== 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
 
                 + ... copy xulrunner/ to this directory

Latest revision as of 14:05, 26 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