osx - How to package a standalone xulrunner app for OS X? -

I am trying to create an Accelerator app for OS X 10.9+. I need it to be a stand alone, i.e. no extra additional software (including firefox) need to be installed on the box with the app.

How do I guide an up-to-date on it? It seems that I have struck every problem described here:

One of the last:

< Pre> $ open MyApp.app to LSOpenURLsWithRole () file failed with error -10810 / path / to MyApp.app.

Here's one I have done so far:

How can I make an OS X? App for the modern (v36 +) xulrunner app?

You are on the right track, just a big problem that you are facing.

If you run the application from the command line, then you will get some output like this.

  $ Sample Application.ApA / Contents / MacOS / Accelerator Mozilla XULRunner 33.0 Usage: Accelerator [Option] Xulrunner APP file [APP option ...] Option - Specify APP file (optional) -H , --help Show this message -V, --version version - Gray-version GRE version string print Application on stdout APP file Initial file APP option option specific options  

As We can see Adan Lable did not automatically say like a tutorial to run content / resource / application.ini that it would be a known issue, and the popular action among XULRunner users is that Xulrunner create a stub shell script to pass the required argument for binary.

There is a script here. 'Just enough to do that is whipped up.

  #! / Bin / s runpath = "` Direeman '$ 0 "`' ContentInender = "` CD "$ Runpath" / .. & gt; / dev / null & pwd "Exec" $ runpath / xulrunner "--app" $ Contentsdir / resources / application.ini " 

Save this file to your MacOS directory and allow it to be executable For example, I have sampling I will use command here to set executable permissions.

  chmod + x sampling  

now, modify info.plist to execute & Lt; Key & gt; CFBundleExecutable & lt; / / instead of executing this code instead of xulrunner . Key & gt; & Lt; String & gt; SampleApplication & lt; / String & gt;

Now when you run your application, it should work. If you are getting an error saying, you want to change the name of the application bundle, or you can follow the advice of that question to avoid the caching problem.

Bonus information

You can remove the Content / Framework / XUL.framework directory, and.

The dependentlibs.list file from content / MacOS to the content / resource directory, though XULRunner 33 without it properly Its going on.