Appearance

Return to top
On this page

TIP

This document is applicable to version 1.6.x, Please use the command ll-cli --version to check your LingLong program version.


Export layer file or uab file

Use ll-builder export to check out the build content and generate layer file or uab file.

View the help information for the ll-builder export command:

bash
ll-builder export --help

Here is the output:

text
Usage: ll-builder [options]

Options:
  -v, --verbose      show detail log (deprecated, use QT_LOGGING_RULES)
  -h, --help         Displays help on commandline options.
  --help-all         Displays help including Qt specific options.
  -f, --file <path>  file path of the linglong.yaml (default is ./linglong.yaml)
  -i, --icon <path>  uab icon (optional)
  -l, --layer        export layer file

The ll-builder export command creates a directory named appid in the project root directory, then checks out the local build cache to this directory, and generate layer file to the build result.

An example of the ll-builder export command is as follows:

Export layer file

bash
ll-builder export --layer

Tips: When the Linglong version is greater than 1.5.6, export defaults to exporting the uab file. If you want to export a layer file, you need to add the --layer parameter

The directory structure after checkout is as follows:

text
linglong.yaml org.deepin.demo_0.0.0.1_x86_64_develop.layer org.deepin.demo_0.0.0.1_x86_64_runtime.layer

Layer files are divided into two categories: binary and develop. The binary includes the application's execution environment, while the develop layer, built upon the binary, retains the debugging environment.

Export Uab File

bash
ll-builder export

The uab file is an offline distribution format used by the LingLong software package, which is not suitable for systems that can normally connect to the LingLong repository. Instead, one should utilize the delta transfer scheme provided by the LingLong software repository to reduce the network transmission size.

Take the org.deepin.demo Linglong application as an example. The directory is as follows:

text
org.deepin.demo
├── entries
│   └── share -> ../files/share
├── files
│   ├── bin
│   │   └── demo
│   └── share
│       ├── applications
│       │   └── demo.desktop
│       └── systemd
│           └── user -> ../../lib/systemd/user
├── info.json
└── org.deepin.demo.install