olca-app-build

Building the distribution packages

To build the distribution packages, we currently use the standard PDE Export wizard. Click on the olca-app project and then on Export... from the context menu. Select Plug-in Development > Eclipse Product from the export wizard and select the following options in the export dialog:

• Configuration: /olca-app/aicpLCA.product (should be the default)
• Root directory: aicpLCA
• Synchronize before exporting: yes [x]
• Destination directory: choose the olca-app-build/build folder of this project
• Generate p2 repository: no [ ] (would be just overhead)
• Export for multiple platforms: yes [x]
• (take the defaults for the others)

In the next page, select the platforms for which you want to build the product. After the export, you need to run the package script package.py to copy resources like the Java runtime, the native math libraries, etc. to the application folder and to create the installers.

The packager script can build distribution packages for the following platforms (but you do not need to build them all, if a platform product is missing it is simply ignored in the package script):

• Linux gtk x86_64
• macOS cocoa x86_64
• Windows win32 x86_64

The packager script may download build tools (7zip, NSIS on Windows), the JRE, and native libraries if these are missing.

Steps when building a release package

Export and package the release (Win, Linux, macOS)

1. Check that the olca-app and olca-modules repositories are on the master branch and are in sync with our GitHub repository.

2. Run the prepare-release.py script that updates the olca-modules libraries in the olca-app, creates fresh database templates, updates the html-pages, creates the Jython bindings from the current modules, etc.:

   cd olca-app
   python prepare-release.py

3. Run the PDE export as described above.

4. Run the packaging script package.py.

   cd olca-app-build
   python package.py

Prepare the independent distribution of the Mac app (.dmg) (only on macOS)

In order to pass the Gatekeeper protection, the Mac bundle freshly packaged has to be signed in depth with an Apple Development certificate, notarized and stapled. When testing, one should make a test copy after running the script.

Prerequisites:

• Xcode (version > 13),
• Keychain Access,
• create-dmg (version > 1.1.0): brew install create-dmg,

1. Set up the signing certificate:

   • Open Settings > Accounts > + and sign in with the Green Delta Apple ID.
   • Add the Developer ID Application Certificate in Manage Certificates....
   • Get the name of the certificate:
     • Open Keychain Access,
     • In login > My Certificates copy the full name Developer ID Application: GreenDelta GmbH (<code>).

2. Set up the notarytoolcredentials:

   • Go to https://appleid.apple.com/ and sign in with the Green Delta Apple ID.
   • Select Application password and create a new password named notarytool-<pseudo> and copy it.
   • Add the password to your system:
     • Run the following command xcrun notarytool store-credentials:
     • Profile name:
     • Path to...:
     • Developer Apple ID:
     • App-specific password:
     • Developer Team ID: <code of the certificate (cf. Developer ID Application: GreenDelta GmbH (<code>))>

3. Run the following command to sign, notarized, staple the app and embellish the disk image:

   cd olca-app-build
   ./mac_dist.sh dmg --dev-id-app <certificate full name> --keychain <password name>

Prepare the App store distribution of the Mac app (.pkg) (only on macOS)

To be continued...

Test the apps!

1. Open every package, open a database and eventually a product system.
2. Test the DMG on a different computer than the one used to sign and notarize.