packager

The levure/packager folder contains the packager.livecodescript stack. This script uses your application's app.yml configuration file to bring together all the necessary resources to package and build the final application ready for distribution.

• 📂 your_project_folder
  • 📂 app
    • app.yml
  • 📁 builds
  • 📂 levure
    • 📂 packager
      • packager.livecodescript

Packaging an Application

Levure will package up an application for distribution. To package your application for a specific build profile call the following handler:

levurePackageApplication pBuildProfile

• Creates a folder named after the build profile in the builds folder.
• Within that folder a folder is created using the version and build number.
• The packaged applications will be placed in folders for each platform you build your application for.
• Any files in your copy files settings will be copied over. Variable replacement will be performed on any files.
• If you are building on OS X and have configured a certificate name then the app will be signed.
• If you are building for a profile named "mas" or "Mac App Store" then the app will be signed, zipped up, and prepared for upload to the Mac App Store.

The build profiles section in app.yml

build profiles:
  all profiles:
    post build script: [relative path to LiveCode file that will be run post build]
    certificates:
      macos:
        name: [name of certificate to sign OS X applications with]
    copy files:
      all platforms:
        - filename: [relative path to file or folder that should be copied to build folder]
          destination: [relative destination folder without build folder]
        ...
      macos:
        ...
      windows:
        ...
      linux:
        ...
      ios:
        ...
      android:
        ...
  development:
  beta:
  release:

copy files

• Learn about including additional files and folders in your application builds

Building executables for testing

The framework supports building stub executables that can be used to launch your app in a standalone environment for testing. By using the stub executables for testing, you can be working on your application in the IDE and instantly test your work running in a standalone.

To build the stub executables open your standalone stack and call the function levureBuildStandalonesForTesting from the message box. The LiveCode standalone builder will be used to build standalones based on your settings. MacOS X, Windows, and Linux standalone files will be moved to a test folder inside of the build folder that you have configured in app.yml.

Version information

There are two properties you will deal with for versioning: version and build. version is in the [major].[minor].[revision] format. This is what you would display to users. build is an integer that you should increment each time you build your application. The build number is used to uniquely identify your application for the Sparkle update framework as well as identify each package in a 'release train' that you submit to the Mac App Store when preparing to release a version to the public. You can start the build number at 1 and then increment by one each time you package your application and send it to someone.