== #REDIRECT:[[How to get use the Poky Yocto Project to develop Embedded Linux distribution ==]]
[http://www.pokylinux.org/about Poky] is an open source platform build tool. It is a complete software development environment for = How to get the creation of Linux devices. It enables you to design, develop, build, debug, and test a complete, modern, software stack using Yocto Linux, the X Window System and GNOME Mobile based application frameworks for both x86 and ARM based platforms. Key features include:distribution =
*Full, fast, cross device filesystem creation with '''It's not an embedded 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 distribution – it creates a custom one for you''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 Much of How-To ===This this How-To is meant extracted from different sources. If you would like to be a starting point for people to learn build and run Poky images for IGEP v2 devices as quickly read some of the original articles or resources, please visit them and easily as possible.thank the authors:
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 The Yocto 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: *The Poky website ( http://www.pokylinuxyoctoproject.org/ )*The Poky Handbook Yocto project documentation ( http://www.pokylinux.org/doc/poky-handbook.html )*Using the Anjuta Poky SDK plugin ( http://pokylinuxyoctoproject.org/blog/index.php/2010/03/using-the-anjuta-poky-sdk-plugin documentation )
*The Openembedded website ( http://www.openembedded.org/ )
=== 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<pre>$ sudo dpkg-reconfigure dash</pre>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<pre>$ sudo nano /etc/sysctl.confvm.mmap_min_addr = 0</pre>then, run this command<pre>$ sudo sysctl -p</pre> Install extra packages necessary for bitbake to function.<pre>$ 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</pre> ==== 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. <pre>$ git clone git://git.igep.es/pub/scm/poky.gitInitialized 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.</pre>Then, switch to stable branch (Purple v3.2)<pre>$ cd poky$ git checkout origin/release/purple -b release/purplewarning: You appear to be on a branch yet to be born.warning: Forcing checkout Overview 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"</pre>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.<pre>$ ln -s ../../meta-contrib/build/conf/local.conf.igep0020 build/conf/local.conf</pre> At this point the Poky build environment needs to be set up, you will do this with the poky-initHow-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. To ==== Poky (development branch) ====The 'master' is where the development work takes place and you should use this if you're after to work with the latest cutting edge developments. It is possible trunk can suffer temporary periods of instability while new features are developed and if this is undesirable we recommend using one of the release branches. Poky (development branch) is available from a GIT repository located at git://git.pokylinux.org/poky.git. The first thing you will do is clone the Poky project. <pre>$ git clone git://git.pokylinux.org/poky.git</pre> After that, you need to create an user configuration (local.conf). The configuration file who defines various configuration variables which govern what Poky platform does. <pre>$ mkdir -p build/conf</pre>And create with your preferred editor the build/conf/local.conf file, the result will be like this: <pre># Where to cache the files Poky downloadsDL_DIR ?= "${OEROOT}/sources"BBFILES += "\ ${OEROOT}/meta/packages/*/*.bb \ ${OEROOT}/meta-moblin/packages/*/*.bb" BBFILE_COLLECTIONS = "normal moblin"BBFILE_PATTERN_normal = "^${OEROOT}/meta/"BBFILE_PATTERN_moblin = "^${OEROOT}/meta-moblin/"
BBFILE_PRIORITY_normal = "5"BBFILE_PRIORITY_moblin = "5"This How-To is meant to be a starting point for people to learn build and run Yocto-based images for IGEP Technology devices as quickly and easily as possible.
# Uncomment and set to allow bitbake to execute multiple tasks at once.# For a quadcore, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would# be appropriate.# BB_NUMBER_THREADS About the Yocto Project™ = "4"# Also, make can be passed flags so it run parallel threads e.g.:# PARALLEL_MAKE = "-j 4"
# The machine [http://www.yoctoproject.org Yocto Project™] is an open source collaboration project that provides templates, tools and methods to targetMACHINE ?= "igep0020b"help you create custom Linux-based systems for embedded products regardless of the hardware architecture. It was founded in 2010 as a collaboration among many hardware manufacturers, open-source operating systems vendors, and electronics companies to bring some order to the chaos of embedded Linux development.
TARGET_FPU_arm ?= "hard"= Why use the Yocto Project™ ==
# Other supported machines#MACHINE ?= "qemux86"#MACHINE ?= "qemuarm"#MACHINE ?= "c7x0"#MACHINE ?= "akita"#MACHINE ?= "spitz"#MACHINE ?= "nokia770"#MACHINE ?= "nokia800"#MACHINE ?= "ficBecause it's a complete embedded Linux development environment with tools, metadata, and documentation -gta01"#MACHINE ?= "bootcdx86"#MACHINE ?= "cm-x270"#MACHINE ?= "em-x270"#MACHINE ?= "htcuniversal"#MACHINE ?= "mx31ads"#MACHINE ?= "mx31litekit"#MACHINE ?= "mx31phy"#MACHINE ?= "netbook"#MACHINE ?= "zylonite"everything you need. The free tools are easy to get started with, powerful to work with (including emulation environments, debuggers, an Application Toolkit Generator, etc.) and they allow projects to be carried forward over time without causing you to lose optimizations and investments made during the project’s prototype phase. The Yocto Project fosters community adoption of this open source technology allowing its users to focus on their specific product features and development
DISTRO ?= "poky"# For bleeding edge / experimental / unstable package versions# DISTRO ?= "poky-bleeding"Build Platform Setup Environment ==
# Poky has various extra metadata collections (openmokoIn order to build an image with BSP support for a given release, extras).# To enable these, uncomment all (or some of) you need to download the following lines:# BBFILES = "\# ${OEROOT}/meta/packages/*/*.bb \# ${OEROOT}/meta-extras/packages/*/*.bb \# ${OEROOT}/meta-openmoko/packages/*/*corresponding BSP repository.bb \# ${OEROOT}/meta-moblin/packages/*/*At this time latest stable branch for IGEP devices is denzil.bb \# "# BBFILE_COLLECTIONS = "normal extras openmoko moblin"# BBFILE_PATTERN_normal = "^${OEROOT}/meta/"# BBFILE_PATTERN_extras = "^${OEROOT}/meta-extras/"# BBFILE_PATTERN_openmoko = "^${OEROOT}/meta-openmoko/"# BBFILE_PATTERN_moblin = "^${OEROOT}/meta-moblin/"# BBFILE_PRIORITY_normal = "5"# BBFILE_PRIORITY_extras = "5"# BBFILE_PRIORITY_openmoko = "5"# BBFILE_PRIORITY_moblin = "5"
BBMASK = "" $ git clone -b denzil git://git.isee.biz/pub/scm/poky.git
# EXTRA_IMAGE_FEATURES allows extra packages to be added Enter to the generated images # (Some of these are automatically added to certain image types)# "dbg-pkgs" - add -dbg packages for all installed packages# (adds symbol information for debugging/profiling)# "dev-pkgs" - add -dev packages for all installed packages# (useful if you want to develop against libs in the image)# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)# "tools-debug" - add debugging tools (gdb, strace)# "tools-profile" - add profiling tools (oprofile, exmap, lttng valgrind (x86 only))# "tools-testapps" - add useful testing tools (ts_printpoky directory, aplay, arecord etc.)# "debug-tweaks" - make an image for suitable of development# e.g. ssh root access has a blank password# There are other application targets too, see meta/classes/poky-image.bbclass # and meta/packages/tasks/task-poky.bb for more details.
EXTRA_IMAGE_FEATURES = "tools-debug tools-profile tools-testapps debug-tweaks" $ cd poky
# The default IMAGE_FEATURES above are too large for the mx31phy and # c700/c750 machines which have limited space. The code below limits# clone the default features for those machinesmeta-isee layer.EXTRA_IMAGE_FEATURES_c7x0 = "tools-testapps debug-tweaks"EXTRA_IMAGE_FEATURES_mx31phy = "debug-tweaks"EXTRA_IMAGE_FEATURES_mx31ads = "tools-testapps debug-tweaks"
# A list of packaging systems used in generated images# The first package type listed will be used for rootfs generation# include 'package_deb' for debs# include 'package_ipk' for ipks#PACKAGE_CLASSES ?= "package_deb package_ipk"PACKAGE_CLASSES ?= "package_ipk" $ git clone -b denzil git://git.isee.biz/pub/scm/meta-isee.git
# POKYMODE controls the characteristics of the generated packages/images by# telling poky which type of toolchain to use.## Options include several different EABI combinations and a compatibility # mode for the OABI mode poky previously used. ## The default is "eabi"# Use "oabi" for machines with kernels < 2.6.18 on ARM for example.# Use "external $ source oe-MODE" to use the precompiled external toolchains where MODE# is the type of external toolchain to use e.g. eabi.# POKYMODE = "externalinit-eabi"build-env
# Uncomment this to specify where BitBake should create its temporary files.# Note Having done that , and assuming you downloaded the BSP contents at the top-level of your yocto build tree, you can build a full build igep image by adding the location of everything in OpenEmbedded will take GigaBytes of hard# disk space, so make sure the 'meta-igep' layer to free enough space'bblayers. The default TMPDIR is# <build directory>/tmpTMPDIR = "${OEROOT}/build/tmp-${MACHINE}"conf'
Add below line into .../poky/build/conf/bblayers.conf:
# Uncomment this if you are using the Openedhand provided qemu deb <path to>/poky/meta- see README# ASSUME_PROVIDED += "qemu-native"isee \
# Comment this out if you donTo enable the isee layer, add the 't have a 3igep00x0 MACHINE' to .x gcc version available and wish# poky to build one for you. The 3.x gcc is required to /poky/build qemu-native/conf/local.# ASSUME_PROVIDED += "gcc3-native"conf:
# Uncomment these two if you want BitBake to build images useful for debugging.# DEBUG_BUILD MACHINE ?= "1"# INHIBIT_PACKAGE_STRIP = "1igep00x0"
# Uncomment these You should then be able to build a package image as such that you can use gprof to profile it.# NOTE: This will only work with 'linux' targets, not# 'linux-uclibc', as uClibc doesn't provide the necessary# object files. Also, don't build glibc itself with these# flags, or it'll fail to build.## PROFILE_OPTIMIZATION = "-pg"# SELECTED_OPTIMIZATION = "${PROFILE_OPTIMIZATION}"# LDFLAGS =+ "-pg"
# Uncomment this if you want BitBake to emit debugging output# BBDEBUG = "yes"# Uncomment this if you want BitBake to emit the log if a build fails.BBINCLUDELOGS = "yes" $ bitbake demo-image-sato
# Specifies At the end of a location to search for pre-generated tarballs when fetching# a cvs:// or svn:// URI. Uncomment thissuccessful build, if you do not want to pull directly# should have an image that you could use for boot device from CVS flash or SubversionSRC_TARBALL_STASH = "http://pokylinuxa micro-SD card.org/sources/"
# Set this if you wish to make pkgconfig libraries from your system == Extending the available # for native builds. Combined packages with extra ASSUME_PROVIDEDs this can allow # native builds of applications like oprofileui-native (unsupported feature).#EXTRA_NATIVE_PKGCONFIG_PATH others layers = ":/usr/lib/pkgconfig"#ASSUME_PROVIDED += "gtk+-native libglade-native"
ENABLE_BINARY_LOCALE_GENERATION = "1"You can append more layers to your environment in order to build more packages, in following wxample you'll download the meta-openembedded layer. In your poky directory
# The architecture to build SDK items for, by setting this you can build SDK# packages for architectures other than the host i.e $ git clone -b denzil git://git. building i586 packages# on an x86_64 hostopenembedded.# Supported values are i586 and x86_64SDKMACHINE="i586"<org/pre>meta-openembedded
At this point Add the Poky layer into 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/conf/bblayers.conf:
=== Poky images supported ===As discussed above the Poky build environment needs <path to be set up using the following command:>/poky/meta-openembedded/meta-oe \
<pre>$ source poky-init-Now you can build-env</pre>Once any of the Poky build environment is set upnew packages added, a target can now be built usingfor example:
<pre> $ bitbake <target></pre>The target is the name of the recipe you want to build. Common targets are the images (in meta/packages/images/) or the name of a recipe for a specific piece of software like busybox. For more details about the images have a look to the [http://www.pokylinux.org/doc/poky-handbook.html Poky Handbook]postgresql
For example, you will build the Sato == Create your own Linux image using the following command:==
<pre>$ bitbake poky-image-sato</pre>After a long time the complete file system images are placed here,TODO
<pre> tmp-igep0020/deploy/images/</pre>and any resulting .ipk packages emitted by Poky are placed here== Yocto 1.2 'denzil' documentation ==
<pre> tmp-igep0020/deploy/ipk/</pre>'''Official documentation'''
==== Images supported for stable branch * [http://www.yoctoproject.org/docs/1.2/yocto-project-qs/yocto-project-qs.html Yocto Project Quick Start]: This short document lets you get started with the Yocto Project quickly and start building an image.* [http://www.yoctoproject.org/docs/1.2/adt-manual/adt-manual.html The Yocto Project Application Development Toolkit (Purple 3ADT) User's Guide]: This manual provides information that lets you get going with the ADT to develop projects using the Yocto Project.* [http://www.yoctoproject.org/docs/1.2/bsp-guide/bsp-guide.html The Yocto Project Board Support Package (BSP) ====Developer's Guide]: This brief document defines a structure for BSP components. Having a commonly understood layout encourages standardization.* [http://www.yoctoproject.org/docs/1.2/dev-manual/dev-manual.html The Yocto Project Development Manual]: This Manual provides an overview of the development process for images and user-space applications.* [http://www.yoctoproject.org/docs/1.2/poky-ref-manual/poky-ref-manual.html The Yocto Project Reference Manual]: This manual is the complete reference guide to the Yocto Project, including the Poky reference system which contains a worki
Refer to http://www.pokylinux.org/doc/poky-handbook.html#ref-images for standard images= See also =
Refer *[[How to get the Angstrom distribution]] *[[Ubuntu804IGEPv20SDKVirtualMachine|How to get the Ubuntu 8.04 IGEP v2.0 SDK Virtual Machinedistribution]] *[[How to get the Linaro distribution]] *[[How to how get the Android distribution]] *[[How to install and use poky images on a NFS-mounted root filesystem.get the Meego distribution]]
--- That's all folks ---[[Category:Software_distributions|Poky]]