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.
==== Poky (development branch) ====The 'master' is where the development work takes place and you should use this if you're after Refer to work with the latest cutting edge developmentshttp://www. 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 branchespokylinux. org/doc/poky-handbook.html#ref-images for standard images
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 Refer to create an user configuration (local[[Ubuntu 8.conf)04 IGEP v2. 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># CONF_VERSION is increased each time build/conf/ changes incompatiblyCONF_VERSION = "1" # Where 0 SDK Virtual Machine]] to cache the files Poky downloadsDL_DIR ?= "${OEROOT}/sources"# Where how to cache Poky's built staging outputPSTAGE_DIR ?= "${OEROOT}/pstage" # Uncomment install 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 = "4"# Also, make can be passed flags so it run parallel threads e.g.:PARALLEL_MAKE = "-j 4" # The machine to target#MACHINE ?= "qemux86"MACHINE ?= "igep0020" # Other supported machines#MACHINE ?= "qemuarm"#MACHINE ?= "netbook"#MACHINE ?= "c7x0"#MACHINE ?= "akita"#MACHINE ?= "spitz"#MACHINE ?= "nokia770"#MACHINE ?= "nokia800"#MACHINE ?= "fic-gta01"#MACHINE ?= "bootcdx86"#MACHINE ?= "cm-x270"#MACHINE ?= "em-x270"#MACHINE ?= "htcuniversal"#MACHINE ?= "mx31ads"#MACHINE ?= "mx31litekit"#MACHINE ?= "mx31phy"#MACHINE ?= "zylonite" DISTRO ?= "use poky"# For bleeding edge / experimental / unstable package versions# DISTRO ?= "poky-bleeding" # Poky has various extra metadata collections (openmoko, extras).# To enable these, uncomment all (or some of) the following lines:# BBFILES = "\# ${OEROOT}/meta/packages/*/*.bb \# ${OEROOT}/meta-extras/packages/*/*.bb \# ${OEROOT}/meta-openmoko/packages/*/*.bb \# ${OEROOT}/meta-moblin/packages/*/*.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 = "" # EXTRA_IMAGE_FEATURES allows extra packages to be added 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_print, 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" # The default IMAGE_FEATURES above are too large for the mx31phy and # c700/c750 machines which have limited space. The code below limits# the default features for those machines.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" # 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-MODE" to use the precompiled external toolchains where MODE# is the type of external toolchain to use e.g. eabi.# POKYMODE = "external-eabi" # Uncomment this to specify where BitBake should create its temporary files.# Note that a full build of everything in OpenEmbedded will take GigaBytes of hard# disk space, so make sure to free enough space. The default TMPDIR is# <build directory>/tmpTMPDIR = "${OEROOT}/build/tmp" # Uncomment this if you are using the Openedhand provided qemu deb NFS- see README# ASSUME_PROVIDED += "qemu-native" # Comment this out if you don't have a 3.x gcc version available and wish# poky to build one for you. The 3.x gcc is required to build qemu-native.# ASSUME_PROVIDED += "gcc3-native" # Uncomment these two if you want BitBake to build images useful for debugging.# DEBUG_BUILD = "1"# INHIBIT_PACKAGE_STRIP = "1" # Uncomment these to build a package 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 failsmounted root filesystem.BBINCLUDELOGS = "yes"
# Set this if you wish to make pkgconfig libraries from your system available # for native builds==== Poky version 3. Combined with extra ASSUME_PROVIDEDs this can allow # native builds of applications like oprofileui-native 3 codename Green (unsupported featureunder development).#EXTRA_NATIVE_PKGCONFIG_PATH = ":/usr/lib/pkgconfig"#ASSUME_PROVIDED += "gtk+-native libglade-native"==
ENABLE_BINARY_LOCALE_GENERATION = "1"Poky version 3.3 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.
# The architecture to build SDK items for, by setting this you can build SDK# packages for architectures other than the host i.e. building i586 packages# on an x86_64 host.# Supported values are i586 and x86_64SDKMACHINE="i586" # Poky can try and fetch packaged-staging packages from a http, https or ftp# mirror. Set this variable to the root of a pstage directory on a server.#PSTAGE_MIRROR ?= "http $ git clone git://someservergit.tldigep.es/sharepub/pstage" INHERIT += "rm_work"scm/poky.git</pre> $ 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.
=== Poky images supported ===As discussed above the Poky build environment needs to be set up using the following command: <pre>$ source poky-init-build-env</pre>Once the Poky build environment is set up, a target can now be built using: <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.pokylinuxPlease contribute .org/doc/poky-handbook.html Poky Handbook] For example, you will build the Sato image using the following command: <pre>$ bitbake poky-image-sato</pre>After a long time the complete file system images are placed here, <pre> tmp-igep0020/deploy/images/</pre>and any resulting .ipk packages emitted by Poky are placed here. <pre> tmp-igep0020/deploy/ipk/</pre> ==== Images supported for stable branch (Purple 3.2) ==== 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.
--- That's all folks ---
[[Category:Software distributions|Poky]]