Hi, according to the ELDK documentation[1], one needs to edit the provided configuration files to start even a first build. It turned out that this phase has potential for a lot of errors, especially using the shared downloads directory is and was a source of confusion. I suggest that we use provided config files that need no to little manual intervention. We can then document the initial setup as
TEMPLATECONF=meta-eldk/conf source oe-init-build-env .... on the wiki[1]. A subsequent "MACHINE=generic-powerpc bitbake core-image-minimal" then works for me without any further change. Attached are patches to make this work against eldk 5.3 (or 5.3.1) and (the not released) eldk 5.4. Cheers Detlev [1] http://www.denx.de/wiki/view/ELDK-5/EldkBuilding -- I object to doing things that computers can do. -- Olin Shivers -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: [email protected]
>From 2e8ee545258e4f52abbedf5534e4eaee839ef6bb Mon Sep 17 00:00:00 2001 From: Detlev Zundel <[email protected]> Date: Fri, 26 Jul 2013 11:35:38 +0200 Subject: [PATCH] meta-eldk/conf: Resync bblayers.conf and local.conf The yocto 1.3 provided samples are synced again with the ELDK documentation to easily start a build with minimal conf file editing like this: TEMPLATECONF=meta-eldk/conf . oe-init-build-env <build-dir> Signed-off-by: Detlev Zundel <[email protected]> --- meta-eldk/conf/local.conf.sample | 380 ++++++++++++++++++++------------------- 1 file changed, 195 insertions(+), 185 deletions(-) diff --git a/meta-eldk/conf/local.conf.sample b/meta-eldk/conf/local.conf.sample index 434c684..3d7b5a1 100644 --- a/meta-eldk/conf/local.conf.sample +++ b/meta-eldk/conf/local.conf.sample @@ -1,219 +1,229 @@ -# CONF_VERSION is increased each time build/conf/ changes incompatibly -CONF_VERSION = "1" - -# Uncomment and change to cache the files Poky downloads in an alternative -# location, default it ${TOPDIR}/downloads -#DL_DIR ?= "${TOPDIR}/downloads" -# Uncomment and change to cache Poky's built staging output in an alternative -# location, default ${TOPDIR}/sstate-cache -#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" - -# 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 = "4" -# Also, make can be passed flags so it run parallel threads e.g.: -# PARALLEL_MAKE = "-j 4" +# +# This file is your local configuration file and is where all local user settings +# are placed. The comments in this file give some guide to the options a new user +# to the system might want to change but pretty much any configuration option can +# be set in this file. More adventurous users can look at local.conf.extended +# which contains other examples of configuration which can be placed in this file +# but new users likely won't need any of them initially. +# +# Lines starting with the '#' character are commented out and in some cases the +# default values are provided as comments to show people example syntax. Enabling +# the option is a question of removing the # character and making any change to the +# variable as required. -# Set a default machine to target unless a machine is selected from the -# lists below. -MACHINE ??= "qemux86" +# +# Parallelism Options +# +# These two options control how much parallelism BitBake should use. The first +# option determines how many tasks bitbake should run in parallel: +# +#BB_NUMBER_THREADS = "4" +# +# The second option controls how many processes make should run in parallel when +# running compile tasks: +# +#PARALLEL_MAKE = "-j 4" +# +# For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would +# be appropriate for example. -# Supported emulation machines +# +# Machine Selection +# +# You need to select a specific machine to target the build with. There are a selection +# of emulated machines available which can boot and run in the QEMU emulator: +# #MACHINE ?= "qemuarm" #MACHINE ?= "qemumips" #MACHINE ?= "qemuppc" #MACHINE ?= "qemux86" #MACHINE ?= "qemux86-64" - -# Supported target hardware for demonstration purposes +# +# There are also the following hardware board target machines included for +# demonstration purposes: +# #MACHINE ?= "atom-pc" #MACHINE ?= "beagleboard" -#MACHINE ?= "emenlow" #MACHINE ?= "mpc8315e-rdb" #MACHINE ?= "routerstationpro" +# +# This sets the default machine to be qemux86 if no other machine is selected: +MACHINE ??= "qemux86" -DISTRO ?= "poky" -# For bleeding edge / experimental / unstable package versions -# DISTRO ?= "poky-bleeding" - -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 -# include 'package_rpm' for rpms -#PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" -PACKAGE_CLASSES ?= "package_rpm package_ipk" - -# mklibs library size optimization is more useful to smaller images, -# and less useful for bigger images. Also mklibs library optimization can break the ABI compatibility, so should not be applied to the images which are tobe -# extended or upgraded later. -#This enabled mklibs library size optimization just for the specified image. -#MKLIBS_OPTIMIZED_IMAGES ?= "poky-image-minimal" -#This enable mklibs library size optimization will be for all the images. -#MKLIBS_OPTIMIZED_IMAGES ?= "all" - -# A list of additional classes to use when building the system -# include 'image-mklibs' to reduce shared library files size for an image -# include 'image-prelink' in order to prelink the filesystem image -# include 'image-swab' to perform host system intrusion detection -# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink -USER_CLASSES ?= "image-mklibs image-prelink" - -# 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. +# Where to place downloads # -# 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>/tmp -#TMPDIR = "${POKYBASE}/build/tmp" +# During a first build the system will download many different source code tarballs +# from various upstream projects. This can take a while, particularly if your network +# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you +# can preserve this directory to speed up this part of subsequent builds. This directory +# is safe to share between multiple builds on the same machine too. +# +# The default is a downloads directory under TOPDIR which is the build directory. +# +DL_DIR ?= "/opt/eldk/downloads" -# The following are used to control options related to debugging. # -# Uncomment this to change the optimization to make debugging easer, at the -# possible cost of performance. -# DEBUG_BUILD = "1" +# Where to place shared-state files +# +# BitBake has the capability to accelerate builds based on previously built output. +# This is done using "shared state" files which can be thought of as cache objects +# and this option determines where those files are placed. # -# Uncomment this to disable the stripping of the installed binaries -# INHIBIT_PACKAGE_STRIP = "1" +# You can wipe out TMPDIR leaving this directory intact and the build would regenerate +# from these files if no changes were made to the configuration. If changes were made +# to the configuration, only shared state files where the state was still valid would +# be used (done using checksums). # -# Uncomment this to disable the split of the debug information into -dbg files -# INHIBIT_PACKAGE_DEBUG_SPLIT = "1" +# The default is a sstate-cache directory under TOPDIR. # -# When splitting debug information, the following controls the results of the -# file splitting. +#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" + # -# .debug (default): -# When splitting the debug information will be placed into -# a .debug directory in the same dirname of the binary produced: -# /bin/foo -> /bin/.debug/foo +# Where to place the build output # -# debug-file-directory: -# When splitting the debug information will be placed into -# a central debug-file-directory, /usr/lib/debug: -# /bin/foo -> /usr/lib/debug/bin/foo.debug +# This option specifies where the bulk of the building work should be done and +# where BitBake should place its temporary files and output. Keep in mind that +# this includes the extraction and compilation of many applications and the toolchain +# which can use Gigabytes of hard disk space. # -# Any source code referenced in the debug symbols will be copied -# and made available within the /usr/src/debug directory +# The default is a tmp directory under TOPDIR. # -PACKAGE_DEBUG_SPLIT_STYLE = '.debug' -# PACKAGE_DEBUG_SPLIT_STYLE = 'debug-file-directory' - -# 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" +#TMPDIR = "${TOPDIR}/tmp" -# 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" - -# Set this if you wish to make pkgconfig libraries from your system available -# for native builds. Combined with extra ASSUME_PROVIDEDs this can allow -# native builds of applications like oprofileui-native (unsupported feature). -#EXTRA_NATIVE_PKGCONFIG_PATH = ":/usr/lib/pkgconfig" -#ASSUME_PROVIDED += "gtk+-native libglade-native" +# +# Default policy config +# +# The distribution setting controls which policy settings are used as defaults. +# The default value is fine for general Yocto project use, at least initially. +# Ultimately when creating custom policy, people will likely end up subclassing +# these defaults. +# +DISTRO ?= "eldk" +# As an example of a subclass there is a "bleeding" edge policy configuration +# where many versions are set to the absolute latest code from the upstream +# source control systems. This is just mentioned here as an example, its not +# useful to most new users. +# DISTRO ?= "poky-bleeding" -ENABLE_BINARY_LOCALE_GENERATION = "1" +# +# Package Management configuration +# +# This variable lists which packaging formats to enable. Multiple package backends +# can be enabled at once and the first item listed in the variable will be used +# to generate the root filesystems. +# Options are: +# - 'package_deb' for debian style deb files +# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) +# - 'package_rpm' for rpm style packages +# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" +# We default to rpm: +PACKAGE_CLASSES ?= "package_ipk" -# The architecture to build SDK items for, by setting this you can build SDK -# packages for architectures other than the host i.e. building i686 packages -# on an x86_64 host. +# +# SDK/ADT target architecture +# +# This variable specified the architecture to build SDK/ADT items for and means +# you can build the SDK packages for architectures other than the machine you are +# running the build on (i.e. building i686 packages on an x86_64 host._ # Supported values are i686 and x86_64 -#SDKMACHINE ?= "i686" - -# 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. -#SSTATE_MIRRORS ?= "\ -#file://.* http://someserver.tld/share/sstate/ \n \ -#file://.* file:///some/local/dir/sstate/" +SDKMACHINE ?= "i686" -# Set IMAGETEST to qemu if you want to build testcases and start -# testing in qemu after do_rootfs. -#IMAGETEST = "qemu" +# +# Extra image configuration defaults +# +# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated +# images. Some of these options are added to certain image types automatically. The +# variable can contain the following options: +# "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) +# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) +# "debug-tweaks" - make an image suitable for development +# e.g. ssh root access has a blank password +# There are other application targets that can be used here too, see +# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. +# We default to enabling the debugging tweaks. +EXTRA_IMAGE_FEATURES = "debug-tweaks" -# By default test cases in sanity suite will be ran. If you want to run other -# test suite or specific test case(e.g. bat or boot test case under sanity suite), -# list them like following. -#TEST_SCEN = "sanity bat sanity:boot" +# +# Additional image features +# +# The following is a list of additional classes to use when building images which +# enable extra features. Some available options which can be included in this variable +# are: +# - 'buildstats' collect build statistics +# - 'image-mklibs' to reduce shared library files size for an image +# - 'image-prelink' in order to prelink the filesystem image +# - 'image-swab' to perform host system intrusion detection +# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink +# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended +USER_CLASSES ?= "buildstats image-mklibs image-prelink add_machine_symlinks" -#Because of the QEMU booting slowness issue(see bug #646 and #618), autobuilder -#may suffer a timeout issue when running sanity test. We introduce variable -#TEST_SERIALIZE here to reduce the time on sanity test. It is by default set -#to 1. Poky will start image and run cases in the same image without reboot -#or kill. If it is set to 0, the image will be copied and tested for each -#case, which will take much time. +# +# Runtime testing of images +# +# The build system can test booting virtual machine images under qemu (an emulator) +# after any root filesystems are created and run tests against those images. To +# enable this uncomment this line +#IMAGETEST = "qemu" +# +# This variable controls which tests are run against virtual images if enabled +# above. The following would enable bat, boot the test case under the sanity suite +# and perform toolchain tests +#TEST_SCEN = "sanity bat sanity:boot toolchain" +# +# Because of the QEMU booting slowness issue (see bug #646 and #618), the +# autobuilder may suffer a timeout issue when running sanity tests. We introduce +# the variable TEST_SERIALIZE here to reduce the time taken by the sanity tests. +# It is set to 1 by default, which will boot the image and run cases in the same +# image without rebooting or killing the machine instance. If it is set to 0, the +# image will be copied and tested for each case, which will take longer but be +# more precise. #TEST_SERIALIZE = "1" -# Set GLIBC_GENERATE_LOCALES to the locales you wish to generate should you not -# wish to perform the time-consuming step of generating all LIBC locales. -# NOTE: If removing en_US.UTF-8 you will also need to uncomment, and set -# appropriate values for IMAGE_LINGUAS and LIMIT_BUILT_LOCALES -# WARNING: this may break localisation! -#GLIBC_GENERATE_LOCALES = "en_GB.UTF-8 en_US.UTF-8" -# See message above as to whether setting these is required -#IMAGE_LINGUAS ?= "en-gb" -#LIMIT_BUILT_LOCALES ?= "POSIX en_GB" +# +# Interactive shell configuration +# +# Under certain circumstances the system may need input from you and to do this it +# can launch an interactive shell. It needs to do this since the build is +# multithreaded and needs to be able to handle the case where more than one parallel +# process may require the user's attention. The default is iterate over the available +# terminal types to find one that works. +# +# Examples of the occasions this may happen are when resolving patches which cannot +# be applied, to use the devshell or the kernel menuconfig +# +# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none +# Note: currently, Konsole support only works for KDE 3.x due to the way +# newer Konsole versions behave +#OE_TERMINAL = "auto" +# By default disable interactive patch resolution (tasks will just fail instead): +PATCHRESOLVE = "noop" -# This value is currently used by PSEUDO to determine if the recipe should -# build both the 32-bit and 64-bit wrapper libraries on a 64-bit build system. -# -# PSEUDO will attempt to determine if a 32-bit wrapper is necessary, but -# it doesn't always guess properly. If you have 32-bit executables on -# your 64-bit build system, you likely want to set this to "0", -# otherwise you could end up with incorrect file attributes on the -# target filesystem. -# -# Default to not build 32 bit libs on 64 bit systems, comment this -# out if that is desired -NO32LIBS = "1" +# +# Shared-state files from other locations +# +# As mentioned above, shared state files are prebuilt cache data objects which can +# used to accelerate build time. This variable can be used to configure the system +# to search other mirror locations for these objects before it builds the data itself. +# +# This can be a filesystem directory, or a remote url such as http or ftp. These +# would contain the sstate-cache results from previous builds (possibly from other +# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the +# cache locations to check for the shared objects. +# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH +# at the end as shown in the examples below. This will be substituted with the +# correct path within the directory structure. +#SSTATE_MIRRORS ?= "\ +#file://.* http://someserver.tld/share/sstate/PATH \n \ +#file://.* file:///some/local/dir/sstate/PATH" -# If you do not use (or have installed) gnome-terminal you will need to -# uncomment these variables and set them to the terminal you wish to use -# when resolving patches which cannot be applied -# Supported shell prefixes for *_TERMCMD and *_TERMCMDRUN ARE: -# GNOME, SCREEN, XTERM and KONSOLE -#TERMCMD = "${KONSOLE_TERMCMD}" -#TERMCMDRUN = "${KONSOLE_TERMCMDRUN}" +# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to +# track the version of this file when it was generated. This can safely be ignored if +# this doesn't mean anything to you. +CONF_VERSION = "1" -- 1.7.11.7
>From c43c3cffd5b416ad215086fe384fab6b7487f92b Mon Sep 17 00:00:00 2001 From: Detlev Zundel <[email protected]> Date: Fri, 26 Jul 2013 11:52:48 +0200 Subject: [PATCH] meta-eldk/conf: Resync bblayers.conf and local.conf The yocto 1.4 provided samples are synced again with the ELDK documentation to easily start a build with minimal conf file editing like this: TEMPLATECONF=meta-eldk/conf . oe-init-build-env <build-dir> Signed-off-by: Detlev Zundel <[email protected]> --- meta-eldk/conf/bblayers.conf.sample | 4 ++++ meta-eldk/conf/local.conf.sample | 6 ++---- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/meta-eldk/conf/bblayers.conf.sample b/meta-eldk/conf/bblayers.conf.sample index 56cd63a..04955f3 100644 --- a/meta-eldk/conf/bblayers.conf.sample +++ b/meta-eldk/conf/bblayers.conf.sample @@ -11,3 +11,7 @@ BBLAYERS ?= " \ ##COREBASE##/meta-yocto-bsp \ ##COREBASE##/meta-eldk \ " +BBLAYERS_NON_REMOVABLE ?= " \ + ##COREBASE##/meta \ + ##COREBASE##/meta-yocto \ + " diff --git a/meta-eldk/conf/local.conf.sample b/meta-eldk/conf/local.conf.sample index 0483c01..84f5a8b 100644 --- a/meta-eldk/conf/local.conf.sample +++ b/meta-eldk/conf/local.conf.sample @@ -17,17 +17,15 @@ # These two options control how much parallelism BitBake should use. The first # option determines how many tasks bitbake should run in parallel: # -#BB_NUMBER_THREADS = "4" +BB_NUMBER_THREADS = "4" # # The second option controls how many processes make should run in parallel when # running compile tasks: # -#PARALLEL_MAKE = "-j 4" +PARALLEL_MAKE = "-j 4" # # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would # be appropriate for example. -BB_NUMBER_THREADS = "4" -PARALLEL_MAKE = "-j 4" # # Machine Selection -- 1.7.11.7
_______________________________________________ eldk mailing list [email protected] http://lists.denx.de/mailman/listinfo/eldk
