Azbooka

Documentation

• Introduction

• Preparing build environment

• Tutorial 1 (target binary)
• Tutorial 2 (EFL)
• Tutorial 3 (packaging)

• Reference manuals

Source code

Source code of Azbooka firmware is provided in form of git repositories. There are three forms of source code:

• target packages (installed on device)
• target code outside of packages (bootloader and kernel)
• build packages (firmware builder, toolchain etc)

Getting target packages

In order to obtain list of target packages in Azbooka firmware, SSH to device and run command dpkg -l. You'll get list of binary packages and their versions.

In order to find source code for binary package, run apt-cache show $package | grep Source. If this command does not output anything, then source package name is the same as binary package name.

In order to get source code of source package, find corresponding repository in  http://git.openinkpot.org/ or  http://git.iplinux.org (Azbooka firmware is built from two repositories).

Then get a repository (e.g. git clone git://git.openinkpot.org/madshelf.git) and check out version you need (e.g. cd madshelf; git checkout asimov/0.1-2).

Getting bootloader

Find out build date (/etc/openinkpot-version in firmware) of firmware.

Clone git repository  http://git.openinkpot.org/uboot-n516.git/ and check out the commit corresponding to build date.

Getting kernel

Find out version of linux-modules-* package installed in firmware. Then clone git repository  http://git.openinkpot.org/linux-2.6.git/ and check out corresponding tag.

Getting build packages

Use iplinux-bootstrap tool to create build environment. Source code for all packages in build environment can be obtained from  http://git.iplinux.org/ and  http://git.openinkpot.org/ by locating corresponding git repository and checking out commit for the build date.