Reference examples of packaged 3rd party 'custom modules' for LEAFOS devices

Reference examples of packaged 3rd party 'custom modules' for LEAFOS devices

Background:

LEAFOS(X86) is an x86-64 Linux-based operating system designed for PC and laptop repurposing. Technically, applications or drivers which can be installed in a 64-bit Ubuntu Desktop environment should also be installable on LEAFOS to expand its functionality. This is now possible with LEAFOS firmware version 3.2.4 or higher versions.

LEAFOS leverages a read-only Linux file system.  However, LEAFOS has been designed (firmware version 3.2.4 or higher) to allow mounting designated 3rd party application(s) upon device bootup or application start thereby extending the core functionality.
To deploy a 3rd party application to LEAFOS, the software first needs to be put into a module (package) compatible with LEAFOS. This packaging is a one-time process. The created package must contain all dependencies (e.g., libraries) required by the 3rd party software that are not already present in the base LEAFOS. The created package file can then be deployed directly to LEAFOS devices (also remotely, with the PMC Endpoint Manager). 

To learn more about how it works, please refer to the following KB articles:
  1. Overview of LEAFOS 3rd party (custom) application support
  2. Technical details – part 1 – How to create 3rd party custom modules for LEAFOS devices
  3. Technical details – part 2 – How to deploy 3rd party custom modules to LEAFOS devices


Reference 3rd party package application and build scripts: 

To provide some examples on how to package 'custom modules' for LEAF OS devices, we have prepared examples of 'custom modules' created from several popular applications, including:
  1. Google Chrome Browser (download)
  2. Microsoft Edge Browser (download)
  3. Firefox Browser (download)
  4. Zoiper softphone (download)
  5. Linphone softphone (download)
From the downloaded zip file (link above), you will find the reference 'build scripts' and 'packaged image' for each application. Specifically: 
  1. "Packaged image" folder - this folder includes the packaged 'custom module' image (aka 'software container' image) for that application. This packaged 'custom module' includes the application binary (based on Ubuntu 64-bit application), necessary library dependencies, and relevant launch application required to pre-set the required configuration parameters specific to the 3rd party application. This packaged 'custom module' image is generated from the corresponding application build script. This packaged 'custom module' can be directly used to deploy onto LEAF OS devices as outlined in Technical details – part 2 – How to deploy 3rd party custom modules to LEAFOS devices.
  2. "Build script" folder - this folder includes all source build scripts for the application.  It includes all software components like application binary and libraries, launch application and build script to package everything into a single 'custom module' image (i.e. software container).
  3. README file - includes the instructions on how to package the application using the sample build script, and the pre-defined 'custom application configurations' parameters which can be used by admin to pre-set the required configuration parameters specific to the 3rd party application.

3rd party (custom) application support limitation

The example packaged custom modules we provided here are for reference only. 
Packaging and installing 3rd party applications is NOT covered by our standard support.  However, you can contract directly with NComputing for a one-time professional service fee and we will package the specified 3rd party applications. Please contact your NComputing representative for more information