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 this page 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 QEMU images||Stock MeeGo images|
All that's required for this is a reasonably modern Linux distribution (e.g. Fedora 13, Ubuntu 9.10).
Get an image or tarball (with a UX) from one of these locations:
$ wget --continue <link to image file>
$ md5sum <image file>
The process for unpacking is slightly different, depending on the type of image.
Please use the instructions at http://wiki.meego.com/Image_Creation#Installation
Unpack the image using MIC2:
sudo mic-chroot --unpack-only -s ~/meego-chroot <image file>.img
~/meego-chroot with your another path if this one is not suitable for your environment.
Note: This directory should not exist before you run mic-chroot.
yum install kpartx
or on non-RPM distros:
apt-get install kpartx
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.
sudo kpartx -a -v ./meego-handset-ia32-aava-mtf-1.1-sda.bin
Please watch the output of this command. For example, 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.
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
sudo kpartx -d -v ./meego-handset-ia32-aava-mtf-1.1-sda.bin
Chroot into the image using
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.
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.