How to get the Poky Linux distribution

Revision as of 12:54, 24 December 2010 by Agustí Fontquerni (talk | contribs)

Revision as of 12:54, 24 December 2010 by Agustí Fontquerni (talk | contribs)

Contents

How to get the Poky Linux distribution

Poky is an open source platform build tool. It is a complete software development environment for the creation of Linux devices. It enables you to design, develop, build, debug, and test a complete, modern, software stack using Linux, the X Window System and GNOME Mobile based application frameworks for both x86 and ARM based platforms. Key features include:

  • Full, fast, cross device filesystem creation with Linux Kernel 2.6.x, GCC, GNU C library, Busybox, networking and much more.
  • Highly configurable and extendable with full documentation, granular feature control, packaging, and wide machine coverage.
  • Developer friendly with QEMU device virtulisation, SDK generation, Anjuta IDE, OProfile and GDB integration.
  • Complete GNOME Mobile platform with the X Window System, Matchbox, GTK+ 2.12, D-Bus, GStreamer and 'Sato' reference implementation.
  • Support for bleeding edge OpenGL user interfaces with the Clutter toolkit.
  • A supported, stable and proven base for real world products built on Linux and open source software.

Overview of How-To

This How-To is meant to be a starting point for people to learn build and run Poky images for IGEP v2 devices as quickly and easily as possible.

This How-To works with the Ubuntu 8.04 IGEP v2.0 SDK Virtual Machine but most of the contents are valid also for other GNU/Linux distributions. We do not issue any guarantee that this will work on other distributions.

This How-To will start out by a Poky Platform Setup Environment introducing you to the Poky environment and the way you can build an Poky-based image.

Next, we will cover the Poky images supported.

Lastly, we will learn how to Installing and Using the Result on a NFS-mounted root filesystem.

Requirements

  • Ubuntu 8.04 IGEP v2.0 SDK Virtual Machine

Feedback and Contributing

At any point, if you see a mistake you can contribute to this How-To.

How to get involved (http://pokylinux.org/support/)

There are many ways to get involved with the Poky project. Poky has a friendly community providing informal support and discussion.

Mailing list

To subscribe send mail to;

poky+subscribe <at> openedhand <dot> com

And follow simple instructions in subsequent reply. Archives are available here.

Bugs

Problems with Poky should be reported in the bug tracker: http://bugzilla.o-hand.com/

IRC

Chat with the Poky development team and community in #poky on freenode.

References

Much of this How-To is extracted from different sources. If you would like to read some of the original articles or resources, please visit them and thank the authors:

Poky Platform Setup Environment

Poky is derivative of the Open Embedded. In order to function properly, the Virtual Machine need some adaptations of the development system.

The first thing we need to do is set Bash as default sh shell, execute

$ sudo dpkg-reconfigure dash

and answer no when asked whether you want to install dash as /bin/sh. So, now, "/bin/sh" file links to "/bin/bash" (not to "/bin/dash").

An other change we need to perform is to change some default settings of the kernel. Edit the /etc/sysctl.conf file as root with your preferred editor and set the vm.mmpap_min_addr to 0

$ sudo nano /etc/sysctl.conf
vm.mmap_min_addr = 0

then, run this command

$ sudo sysctl -p

Install extra packages necessary for bitbake to function.

$ sudo apt-get update
$ sudo aptitude install subversion cvs git-core \
       build-essential help2man diffstat texi2html texinfo \
       libncurses5-dev gawk python-dev python-psyco python-pysqlite2 \
       scrollkeeper gnome-doc-utils gettext automake mercurial libx11-dev \
       libgl1-mesa-dev libglu1-mesa-dev libsdl1.2-dev

Poky version 3.2 codename Purple (stable branch)

Poky version 3.2 ( stable branch) is available from a GIT repository located at git://git.igep.es/pub/scm/poky.git. The first thing you will do is clone the Poky project.

$ git clone git://git.igep.es/pub/scm/poky.git
Initialized empty Git repository in /home/eballetbo/Software/staging/poky/.git/
remote: Counting objects: 52944, done.
remote: Compressing objects: 100% (16209/16209), done.
remote: Total 52944 (delta 34820), reused 52910 (delta 34806)
Receiving objects: 100% (52944/52944), 35.52 MiB | 249 KiB/s, done.
Resolving deltas: 100% (34820/34820), done.

Then, switch to stable branch (Purple v3.2)

$ cd poky
$ git checkout origin/release/purple -b release/purple
warning: You appear to be on a branch yet to be born.
warning: Forcing checkout of origin/release/purple.
Branch release/purple set up to track remote branch refs/remotes/origin/release/purple.
Switched to a new branch "release/purple"

After that, you need to link an user board configuration (local.conf). The configuration file who defines various configuration variables which govern what Poky platform does.

$ ln -s ../../meta-contrib/build/conf/local.conf.igep0020 build/conf/local.conf

At this point the Poky build environment needs to be set up, you will do this with the poky-init-build-env script. Sourcing this file in a shell makes changes to PATH and sets other core bitbake variables based on the current working directory.

Refer to http://www.pokylinux.org/doc/poky-handbook.html#ref-images for standard images

Refer to Ubuntu 8.04 IGEP v2.0 SDK Virtual Machine to how to install and use poky images on a NFS-mounted root filesystem.

Poky version 3.3 codename Green (under development)

The Poky handbook guides users through getting started with Poky and explains how the build system components fit together and interact. The setup and use of the SDK is also covered along with other common development tasks such as debugging and profiling applications. It also contains extensive reference material on many other aspects of Poky such as the classes, variables and other technical details.

A customized Poky version 3.3 for IGEP platforms is available from a GIT repository located at git://git.igep.es/pub/scm/poky.git.

The first thing you will do is clone the Poky project.

$ git clone git://git.igep.es/pub/scm/poky.git
$ cd poky

At this point the Poky build environment needs to be set up, you will do this with the poky-init-build-env script. Sourcing this file in a shell makes changes to PATH and sets other core bitbake variables based on the current working directory.

... Please contribute ...

--- That's all folks ---