Skip to content

Building packages

Jump to bottom
yzatslinear edited this page Oct 29, 2014 · 13 revisions

In order to build packages for the LTP5903, you will need a Virtual Machine (VM) with the bitbake and OpenEmbedded build components.

The VM can be downloaded from ltp5903-toolchain-vm.

You will need 7z to unarchive the VirtualBox VM. Unarchive the VM to a local disk and "Add" the VM in VirtualBox.

Once you have the VM up and running, connect to the VM using SSH (details in the link above) and follow these steps to build a package:

On the LTP5903 Toolchain VM, clone this repository. It is important to build from the branch that matches your Manager version, otherwise you may introduce incompatible packages.

$ git clone https://github.com/dustcloud/ltp5903-packages.git

Note: If you plan to use this VM for building both 2.x and 4.x packages, you should rename the directory 'ltp5903-packages' to something like ltp5903-packages-4.x. Doing so after invoking bitbake will produce errors and require you to rebuild the toolchain. The examples below use the original name.

Setup the build environment.

$ cd ltp5903-packages
$ git checkout 4.x-stable
$ . oe-setup.sh

Use bitbake to build package(s).

$ bitbake bash

The first time you build a package from a clean directory, it will take a long time to complete (1-2 hours) because it builds the whole toolchain and other package dependencies. Subsequent builds in the same directory will be much quicker because the previously built toolchain will be reused.

Find .ipk file(s) in tmp/deploy/glibc/ipk/armv5te. You may wish to create a symlink to the ipkg directory.

$ ln -s tmp/deploy/glibc/ipk/armv5te ipkgs

Often the recipe will build multiple packages to separate libraries, tools or documentation. It conserves space to only install the packages that are necessary.

The resulting packages can be copied to the LTP5903 Manager and installed.

dust@manager$ sudo ipkg install foo.ipk
Clone this wiki locally