Page History
...
| Tabs Container | |||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||
|
Bolt‑Based Web Application
To build a Bolt‑based web application, you will need the following:
- Bolt Tools
- App package configuration
- Certificates for signing the app bundle
1. Bolt Tools
Install and set up bolt-tools on your system by following the instructions in the repository:
https://github.com/rdkcentral/bolt-tools/tree/main
Bolt Tools provides the utilities required to package and sign your Bolt applications.
2. App Package Configuration
The app package configuration defines the entry point, dependencies, permissions, and other metadata required for building the Bolt package.
2.1 Key Fields:
- Entry Point
For a web application, the entry point should be the URL that the WPE WebKit browser should load.Example: "--url=https://lightningjs.io/tmdb/#splash"
- Dependencies:
Specify the runtime and base Bolt packages your app depends on.
For web apps, you must include the WPE browser package and its appropriate version.Example: "com.rdkcentral.wpe-rdk": "0.1.0"
- Permissions:
Permissions required by the container, such as:- internet
- thunder
- firebolt
- rialto
Sample App Configuration (JSON)
| Code Block |
|---|
{
"id": "com.rdkcentral.appName",
"version": "0.1.0",
"versionName": "develop",
"name": "tmdb",
"packageType": "application",
"entryPoint": "--url=https://lightningjs.io/tmdb/#splash",
"dependencies": {
"com.rdkcentral.wpe-rdk": "0.1.0"
},
"permissions": [
"urn:rdk:permission:internet",
"urn:rdk:permission:firebolt",
"urn:rdk:permission:thunder",
"urn:rdk:permission:rialto"
],
"configuration": {}
} |
...
| title | Testing on Beta Apps |
|---|
For testing the beta wpe browser bolt (wpe+0.2.0) , the entry point configurations need to be set a bit differently :
...
3. Creating a Bolt Package
To package an HTML/Lightning app into a Bolt bundle, you need:
- A JSON configuration file (
com.rdkcentral.app_name.json) - A rootfs layer in
.tgzformat
For HTML/Lightning applications, the rootfs layer can be an empty .tgz file, since the app is launched via a browser using a URL.
Steps
- Create an empty
.tgzfile, e.g.:empty.tgz - Create your App Package configuration JSON file.
- Run the Bolt pack command:
bolt pack com.rdkcentral.app_name.json empty.tgz - The command will generate:
This is the Bolt package to be installed on the platform.com.rdkcentral.app_name+<version>.bolt
4. Signing Your Bolt App
Every Bolt app must be digitally signed before installation.
Follow the signing instructions here:
https://wiki.rdkcentral.com/spaces/RDKM/pages/447124247/Bolt+package+-+signing+and+verification
5. Sideloading the Bolt App to the Platform
...
/tmp/com.rdkcentral.app_name+0.1.0.bolt
...
| Code Block |
|---|
curl -X POST http://127.0.0.1:9998/jsonrpc -d '{"jsonrpc":2.0,"id":1,"method":"org.rdk.PackageManagerRDKEMS.install","params":{"packageId":"com.rdkcentral.app_name+0.1.0.bolt","version":"0.1.0","fileLocator":"/tmp/com.rdkcentral.app_name+0.1.0.bolt"}}' -H "Content-Type: application/json" |
...
| Code Block |
|---|
curl -s -X POST http://127.0.0.1:9998/jsonrpc -d '{"jsonrpc": "2.0","id": 1013, "method": "org.rdk.AppManager.1.launchApp", "params":{"appId":"com.rdkcentral.app_name"}}' |
|
Bolt-based Native Applications
This page describes the process for creating and building native Bolt applications within the RDK ecosystem. The meta-bolt-youtube repository serves as the canonical reference implementation throughout this article.
See also: meta-bolt-distro | bolt-tools | Bolt Package Store
Overview:
A native Bolt application is a self-contained, application packaged as `.bolt` . Each application is maintained in its own Yocto meta-layer repository and follows a shared set of conventions across all RDK Bolt projects.
The overall workflow is:
- Create a new application repository following the standard naming and layout.
- Declare all build-time dependencies in manifests/deps.xml.
- Add or reuse Yocto image recipes and native app recipes.
- Define package configs that instruct the Bolt tool how to assemble the final package.
- Source the build environment and run the Bolt make command.
2. Repository Setup
2.1 Naming Convention
All RDK Bolt application repositories follow this naming pattern:
| Code Block |
|---|
meta-bolt-<app_name> |
Examples:
- meta-bolt-youtube (canonical reference)
- meta-bolt-cobalt
- meta-bolt-myapplication
2.2 Repository Structure
A new meta-bolt repository is expected to contain the following top-level layout:
| Code Block | ||
|---|---|---|
meta-bolt-<app_name>/
├── README.md
├── CONTRIBUTING.md
├── LICENSE
├── COPYING
├── CHANGELOG.md
├── NOTICE
├── manifests/ # dependency declarations (see Section 3)
├── package-configs/ # Bolt package configuration JSON files (see Section 6)
├── recipes-core/ # image recipes (see Section 4)
├── recipes-devtools/ # host-tool recipes
├── recipes-extended/ # native app recipes and bbappend files (see Section 5)
├── conf/ # Yocto layer configuration
└── setup-environment # reusable environment setup script (see Section 7)
|
...
To create the folder:
| Code Block | |
|---|---|
mkdir manifests
|
...
|
...
|
...
|
...
...
...
...
|
...
|
...
...
...
|
...
|
...
|
Overview
Community Forums
Content Tools
Tasks