SDK/Docs/1.2/Building a MeeGo chroot on Linux

This document describes how to create a MeeGo chroot environment from a stock image.

If you want a really quick method for developing on MeeGo where you don't need to build the chroot, use a MeeGo SDK download. The MeeGo SDK includes images tailored for QEMU and the needs of application development. See SDK/Docs/1.2/Getting started with the MeeGo SDK for Linux for details.

However, it can be useful to develop or test on a specific image, such as a recent weekly build. In this case, you may want to build your own chroot environment by following the steps below. However, additional disk space and manual steps may be needed to use these images; and features such as QEMU may not always be usable.

To help you decide what you need, here are the differences between stock MeeGo OS images and MeeGo SDK images:

MeeGo SDK images	Stock MeeGo images
Full OS without applications to reduce image size Have -devel packages installed by default Handset image works in QEMU (x86 netbook kernel is used)	Full OS with applications Don't have -devel packages by default (can be manually installed, see below) Some of the handset images have a Moorestown kernel and don't work in QEMU; the Pinetrail MTF images work sometimes, but inconsistently

Contents 1 Pre-requisites 2 Download and unpack a MeeGo image 2.1 Download tips 2.2 Installing MeeGo Image Creator (MIC) 2.3 Unpacking a .img netbook image 2.4 Unpacking a .bin handset image 3 Using the chroot 3.1 Install developer packages

Pre-requisites

All that's required for this is a reasonably modern Linux distribution (e.g. Fedora 13, Ubuntu 9.10).

Download and unpack a MeeGo image

Get an image or tarball (with a UX) for either netbook or handset from one of these locations:

1. Release images
   • The release images (well tested) can be found here: http://meego.com/downloads/
2. Recently-built images
   • These images have been smoke tested, but may have issues. They can be found here: http://repo.meego.com/MeeGo/builds/trunk/.
   • Follow the links to the directory with the image type you want: for example, you might drill down from there through 1.1.80.4.20101102.1 > handset >images > meego-handset-ia32-mtf. The image file will be either uncompressed (*.img) or compressed (*-sda.bin.bz2).

Download tips

• Network: If your network connection is imperfect you should use a download tool that can continue if the connection is broken, such as wget:

$ wget --continue <link to image file>

• Checksum: Verify the checksum of the downloaded image. The correct checksum is included in the MANIFEST file in the same location as the image file. o generate the checksum from the downloaded file, run the following after downloading (on Linux, at least):

$ md5sum <image file>

The process for unpacking is slightly different, depending on the type of image.

Installing MeeGo Image Creator (MIC)

Please use the instructions at http://wiki.meego.com/Image_Creation#Installation

Unpacking a .img netbook image

1. Unpack the image using MIC:
   

   sudo mic-chroot --unpack-only -s ~/meego-chroot <image file>.usbimg

Replace ~/meego-chroot with your another path if this one is not suitable for your environment.

Unpacking a .bin handset image

1. Install kpartx (a tool for creating device maps from partition tables: because the handset images are raw disk images, this tool can be used to create a device map from the disk image, which can then be mounted on the filesystem)
   

   yum install kpartx

   or on non-RPM distros:

   apt-get install kpartx

2. Unpack the image:
   

   bunzip2 meego-handset-ia32-aava-mtf-1.1-sda.bin.bz2

   This leaves you with a raw disk image you're interested in. (meego-handset-ia32-aava-mtf-1.1-sda.bin.bz2 is a release image from http://meego.com/downloads/.)
   Note you need an Aava image for Atom rather than an N900 image for ARM.

3. Create a device map from the raw image:
   

   sudo kpartx -a -v ./meego-handset-ia32-aava-mtf-1.1-sda.bin
   

   Please watch the output of this command. For exmaple, the output may be "add map loop0p1 (252:2): 0 3320312 linear /dev/loop0 1". This means that the first partition (p1) of the disk image is mapped onto the loop device /dev/loop0. You can then use /dev/mapper/loop0p1 to access the partition.

4. Mount the device map and copy the filesystem into the chroot location:
   

   mkdir ~/tmp-mnt   # temporary mount point
   sudo mount /dev/mapper/loop0p1 ~/tmp-mnt -o loop,ro
   mkdir ~/meego-chroot
   sudo rsync -av ~/tmp-mnt ~/meego-chroot
   sudo umount ~/tmp-mnt
   

5. Remove the device map:
   

   sudo kpartx -d -v ./meego-handset-ia32-aava-mtf-1.1-sda.bin
   

6. Remove the temporary mount point:
   

   rmdir ~/tmp-mnt
   

Using the chroot

Chroot into the image using mic-chroot.

To use the script with the unpacked chroot:

sudo mic-chroot ~/meego-chroot

Once you are inside the chroot, all of the standard MeeGo command line tools are available. This makes it possible to install new software using zypper, run applications etc.

Install developer packages

The MeeGo OS images do not have many necessary devel packages installed. From inside the MeeGo chroot terminal, run the following to install the same set of -devel packages as the SDK image (tailor for your needs). You might need to set http proxy before installing the packages.

$ export http_proxy=<your proxy> (optional)
$ zypper install man qt-creator qt-devel make libmeegotouch-devel gcc gcc-c++ gdb wget

Note: The first time you try to install something, you might get warnings such as the following:

Building repository 'adobe' cache [done]
Signature verification failed for file 'repomd.xml' from repository 'core'.
Warning: This might be caused by a malicious change in the file!
Continuing might be risky. Continue anyway? [yes/no] (no):

Answer yes at the prompts.

See MeeGo SDK with Xephyr for more information about using a chroot for development.