Build and Test

Version added 07-Mar-2018| Modified 10-Jun-2019

After developing the web app, you must build the app and verify its functionality.

Add Recipe File

webOS OSE uses OpenEmbedded of Yocto project to build its components. You must write a recipe that configures the build environment. For more details about the recipe, see Yocto project reference manual.

  • Create and update the file : <web-app-name>.bb

    • Directory : build-webos/meta-webosose/meta-webos/recipes-webos/<web-app-name>

where <web-app-name> is the name of the web app. For the sample web app, <web-app-name> must be replaced by "".

SECTION = "webos/apps"
LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/Apache-2.0;md5=89aea4e17d99a7cacdbeed46a0096b10"
PR = "r0"
inherit webos_component
inherit webos_submissions
inherit webos_cmake
inherit webos_app
inherit webos_arch_indep
FILES_${PN} += "${webos_applicationsdir}"

A brief explanation of the above file:

  • Line(1~3) : Basic descriptions of the component.

  • Line(5) : Version of the component. For the webOS OSE component, this field is mandatory.

  • Line(6) : Revision version of the recipe. Each recipe requires a counter to track its modification history. Make sure that you increment the version when you edit the recipe, unless you only change the value of the WEBOS_VERSION field or comments.

  • Line(8) : Inherit common functions of webOS OSE. For all components of webOS OSE, this entry is required.

  • Line(9) : Instruct OpenEmbedded to use the WEBOS_VERSION value as the component version number. If you develop your component on a local repository, this entry is required.

  • Line(10) : Instruct OpenEmbedded that the component uses CMake for configuration, which is the preferred choice for webOS components.

  • Line(11) : Inherit webos_app, because the component is an app.

  • Line(12) : Inherit webos_arch_indep, because the web app is CPU architecture independent. When inheriting from webos_arch_indep, ensure that your project command in the CMake script specifies NONE as the language, i.e. project(<component> NONE). Otherwise, CMake will attempt to find the C and C++ compilers. Your component may well be built before the toolchain, resulting in a failure to build.

  • Line(14) : ${webos_applicationsdir} indicates /usr/palm/applications${PN} is a package name, which is set to

Configure Local Source Directory

To build a component that is located on the local system, you must specify the directory information.

  • Create and update the file : webos-local.conf

    • Directory : build-webos

For the sample web app (, you must provide the local path where the source exists.

INHERIT += "externalsrc" = "/home/username/project/" = "/home/username/project/" =".local0"

A brief explanation of the above file:

  • Line(1) : Inherit "externalsrc" bbclass file.

  • Line(2) : The local source directory. The syntax of the property is EXTERNALSRC_pn-<component>.

  • Line(3) : The local build directory. The syntax of the property is EXTERNALSRC_BUILD_pn-<component>.

  • Line(4) : The appended revision version (PR) for building local source files. The syntax of the property is PR_append_pn-<component>. This property is optional.

We recommend that you add a trailing slash (/) at the end of all local directory paths, as in Line(2) and Line(3).

Build, Run, and Verify

  1. Build the web app.

    To build the component on the OpenEmbedded environment, enter the following commands on the shell.

    build-webos$ source oe-init-build-env 
    build-webos$ bitbake

    For more information, see Building webOS OSE.


  2. Copy the IPK to the target.

    When the build is successful, oe-related directories are created under the project root directory. These directories are linked to the directory where the build output is generated from the actual build-webos sub-directory.
    ├── CMakeLists.txt
    ├── appinfo.json
    ├── build
    ├── icon.png
    ├── index.html
    ├── oe-logs -> /home/username/build/build-webos/BUILD/work/all-webos-linux/
    ├── oe-workdir -> /home/username/build/build-webos/BUILD/work/all-webos-linux/
    └── webOSjs-0.1.0
        ├── LICENSE-2.0.txt
        └── webOS.js

    If you go to oe-workdir/deploy-ipks/all, you can see file.

    Copy the IPK file to the target device using the scp command.$ scp root@


  3. Install the app on the target.

    Connect to the target using the ssh command and install

    $ ssh root@
    root@raspberrypi3:~# cd /media/internal/downloads/
    root@raspberrypi3:/media/internal/downloads# opkg install
    Installing (1.0.0) on root.
    No image conversions needed for


  4. Discover the LS2 configuration files.

    To make LS2 daemon scan the LS2 configuration files of the app, use the ls-control command as follows.

    root@raspberrypi3:/media/internal/downloads# ls-control scan-services
    telling hub to reload setting and rescan all directories
    For the built-in web app, LS2 configuration files are generated during the build in step 1. To run the app properly, you must make the system scan the newly generated configuration files.


  5. Scan the app.

    To make System and Application Manager (SAM) scan the app, restart SAM using the systemctl command. This step is required so that the app can be added to the app list, which in turn makes the app appear on the Home Launcher.

    root@raspberrypi3:/# systemctl restart sam
    Rebooting the target after step 3 will have the same effect as running step 4 and step 5. However, using the commands in step 4 and step 5 allows you to continue testing without rebooting.


  6. Run the web app.

    Use the Windows key on keyboard to display the Home Launcher. Click the app icon to see the window titled "Web app sample" with the following page:



  7. Verify the execution of the web app.

    • Using SAM

      You can check whether the app is running by using SAM. For more SAM methods, see com.webos.service.applicationmanager.

      root@raspberrypi3:/# luna-send -i -f luna://com.webos.service.applicationmanager/running '{"subscribe":true}'
          "subscribed": true,
          "running": [
                  "id": "",
                  "webprocessid": "1827",
                  "defaultWindowType": "card",
                  "appType": "web",
                  "processid": "1827"
          "returnValue": true
    • Using logs

      You can check the app's log in /var/log/messages on target. Open the file and find "UTC" keyword.

      2019-05-16T02:29:15.322750Z [1517.986582763] WebAppMgr [] GETTIME_SUCCESS {"APP_NAME":"example web app"} UTC : 1557973755
Except as noted, this content is licensed under Creative Commons Attribution 4.0 and sample code is licensed under Apache License 2.0.