M7350v1_en_gpl

oe-core/build/conf/bblayers.conf

@@ -0,0 +1,9 @@
+# This configuration file is dynamically generated every time
+# set_bb_env.sh is sourced to set up a workspace.  DO NOT EDIT.
+#--------------------------------------------------------------
+LCONF_VERSION = "4"
+
+export WORKSPACE := "${@os.path.abspath(os.path.join(os.path.dirname(bb.data.getVar('FILE', d)),'../../..'))}"
+
+BBFILES ?= ""
+BBLAYERS = "/home/lxw2010/M7350v1_v2/apps_proc/oe-core/meta-msm /home/lxw2010/M7350v1_v2/apps_proc/oe-core/meta"

oe-core/build/conf/get_bblayers.py

@@ -0,0 +1,52 @@
+# Generate the bblayers.conf file for the current build workspace
+# emitted to stdout for simplicity.
+
+import os, sys, fnmatch, re
+from operator import itemgetter
+
+# Trawl the OEROOT as passed to us and find all the layer files that meet our
+# metadata directory criteria...
+def getLayerPaths(target,  fnexpr) :
+    retList = []
+    for file in os.listdir(target) :
+        if fnmatch.fnmatch(file, fnexpr) and not (fnmatch.fnmatch(file, "meta-hob") or fnmatch.fnmatch(file, "meta-skeleton")) :
+            # Found what might be a metadata layer...
+            layerPath = target + "/" + file
+            layerConfPath = layerPath + "/conf/layer.conf"
+            if os.path.exists(layerConfPath) :
+                # Found a layer.  Find the priority for it...
+                confFile = open(layerConfPath, "r")
+                if (confFile != None) :
+                    for line in confFile :
+                        fields = line.split()
+                        if (len(fields) > 0 and re.match("BBFILE_PRIORITY",  fields[0])) :
+                            # Add the path, priority as a tuple to the list for the layer.
+                            retList += [( layerPath,  int(fields[2].strip("\"")) )]
+                            break
+                    confFile.close()
+    # In order to avoid potential namespace conflicts, between recipes on layers
+    # we sort the list in descending order of priority.
+    return sorted(retList,  key=itemgetter(1), reverse=True)
+
+
+# Just spool the tuple list's paths out in order to a string...
+def generatePathString ( pathList ):
+    retString = ""
+    for path, priority in pathList:
+        retString = retString + path + " "
+    return retString.strip()
+
+
+# Emit our config file...
+print "# This configuration file is dynamically generated every time" 
+print "# set_bb_env.sh is sourced to set up a workspace.  DO NOT EDIT."
+print "#--------------------------------------------------------------"
+print "LCONF_VERSION = \"4\""
+print
+print "export WORKSPACE := \"${@os.path.abspath(os.path.join(os.path.dirname(bb.data.getVar('FILE', d)),'../../..'))}\""
+print 
+print "BBFILES ?= \"\""
+print "BBLAYERS = \"" + generatePathString(getLayerPaths(sys.argv[1].strip("\""), sys.argv[2].strip("\""))) + "\""
+
+
+

oe-core/build/conf/local.conf

@@ -0,0 +1,218 @@
+#
+# 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 don'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.
+
+#
+# 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 ?= "8"
+# 
+# The second option controls how many processes make should run in parallel when
+# running compile tasks:
+#
+PARALLEL_MAKE ?= "-j 8"
+#
+# For a quadcore, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
+# be appropriate for example.
+
+#
+# Machine Selection
+#
+MACHINE ?= "mdm9625"
+
+#
+# Where to place downloads
+#
+# During a first build the system will download many differernt 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 ?= "${TOPDIR}/downloads"
+
+# Create tarballs when pulling from a source control repository.
+BB_GENERATE_MIRROR_TARBALLS="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 through of as cache objects
+# and this option determines where those files are placed.
+#
+# You can wipe out TMPDIR leaving this directory intact and the build would regenerate
+# from these files if no chages 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).
+#
+# The default is a sstate-cache directory under TOPDIR.
+#
+SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
+
+#
+# Where to place the build output
+#
+# 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 complation of many applications and the toolchain
+# which can use Gigabytes of hard disk space.
+#
+# The default is a tmp directory under TOPDIR.
+#
+TMPDIR = "${TOPDIR}/tmp"
+
+#
+# Default policy config
+#
+# The distribution setting controls which policy settings are used as defaults.
+#
+DISTRO ?= "msm"
+
+#
+# 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"
+PACKAGE_CLASSES ?= "package_ipk package_deb"
+
+#
+# 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"
+
+#
+# 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 (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 that can be uses here too, see 
+# meta/classes/core-image.bbclass and meta/recipes-core/tasks/task-core.bb for more details.
+# We default to enabling the debugging tweaks.
+#EXTRA_IMAGE_FEATURES = "debug-tweaks"
+
+#
+# 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:
+#   - '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 ?= "buildname image-mklibs image-prelink"
+
+# ${BUILDNAME} is used to set the content of /etc/version
+BUILDNAME = "${@get_git_latest_tag('${WORKSPACE}/.repo/manifests', d)}"
+
+#
+# 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, oot test case under sanity suite and 
+# toolchain tests
+#TEST_SCEN = "sanity bat sanity:boot toolchain"
+#
+# 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. This 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 longer but be more precise.
+#TEST_SERIALIZE = "1"
+
+#
+# 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 to use xterm.
+#
+# Examples of the occasions this may happen are when resolving patches which cannot
+# be applied, to use the devshell or the kernel menuconfig
+#
+# If you do not use (or have installed) xterm you will need to
+# uncomment these variables and set them to the terminal you wish to use
+# 
+# Supported shell prefixes for *_TERMCMD and *_TERMCMDRUN are:
+# GNOME, SCREEN, XTERM and KONSOLE
+# Note: currently, Konsole support only works for KDE 3.x due to the way
+# newer Konsole versions behave
+# ---------------------------------------------------------------------------
+# Default to SCREEN mode operations since this could be on a headless system.
+TERMCMD = "${SCREEN_TERMCMD}"
+TERMCMDRUN = "${SCREEN_TERMCMDRUN}"
+
+# By default disable interactive patch resolution (tasks will just fail instead):
+PATCHRESOLVE = "noop"
+
+#
+# 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.
+#SSTATE_MIRRORS ?= "\
+#file://.* http://someserver.tld/share/sstate/ \n \
+#file://.* file:///some/local/dir/sstate/"
+
+
+# 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"
+
+# BB_HASHBASE_WHITELIST Tells bitbake to ignore variables
+# The default list is reproduced here from meta/conf/bitbake.conf
+# Because appending to it was not working
+# The WORKSPACE variable is added through build/conf/bblayers.conf
+BB_HASHBASE_WHITELIST = "TMPDIR FILE PATH PWD BB_TASKHASH BBPATH DL_DIR SSTATE_DIR THISDIR FILESEXTRAPATHS FILE_DIRNAME HOME LOGNAME SHELL TERM USER FILESPATH STAGING_DIR_HOST STAGING_DIR_TARGET COREBASE PRSERV_HOST PRSERV_PORT PRSERV_DUMPDIR PRSERV_DUMPFILE PRSERV_LOCKDOWN PARALLEL_MAKE EXTERNAL_TOOLCHAIN"
+BB_HASHBASE_WHITELIST += "WORKSPACE LICENSE_DIR"

oe-core/build/conf/sanity_info

@@ -0,0 +1,3 @@
+SANITY_VERSION 1
+TMPDIR /home/lxw2010/M7350v1_v2/apps_proc/oe-core/build/tmp-eglibc
+SSTATE_DIR /home/lxw2010/M7350v1_v2/apps_proc/oe-core/build/sstate-cache

oe-core/build/conf/set_bb_env.sh

@@ -0,0 +1,103 @@
+# Let bitbake use the following env-vars as if they were pre-set bitbake ones.
+# (BBLAYERS is explicitly blocked from this within OE-Core itself, though...)
+if [[ ! $(readlink $(which sh)) =~ bash ]]
+then
+  echo ""
+  echo "### Please Change your /bin/sh symlink to point to bash. ### "
+  echo ""
+  echo "### sudo ln -sf /bin/bash /bin/sh ### "
+  echo ""
+  export SHELL=/bin/bash
+fi
+umask 022
+unset MACHINE
+
+# Find where the global conf directory is...
+scriptdir="$(dirname "${BASH_SOURCE}")"
+# Find where the workspace is...
+WS=$(readlink -f $scriptdir/../../..)
+
+# Dynamically generate our bblayers.conf since we effectively can't whitelist
+# BBLAYERS (by OE-Core class policy...Bitbake understands it...) to support
+# dynamic workspace layer functionality.
+python $scriptdir/get_bblayers.py ${WS}/oe-core \"meta*\" > $scriptdir/bblayers.conf
+
+# Edit the upstream .gitignore to ignore the build and bitbake dirs
+echo build   >> ${WS}/oe-core/.gitignore
+echo bitbake >> ${WS}/oe-core/.gitignore
+
+# Convienence function provided for backwards compat with the
+# earlier versions of the QuIC provided OE Linux distro.
+build9615() {
+  export MACHINE=9615-cdp
+  cdbitbake 9615-cdp-image && \
+  cdbitbake 9615-cdp-recovery-image
+}
+
+build9625() {
+  export MACHINE=mdm9625
+  cdbitbake mdm-image && \
+  cdbitbake mdm-recovery-image
+}
+
+buildperf9625() {
+  export MACHINE=mdm9625-perf
+  cdbitbake mdm-perf-image
+}
+
+buildboth9625() {
+  build9625 && \
+  buildperf9625
+}
+
+build8655() {
+  export MACHINE=msm8655
+  cdbitbake msm-x11-image
+}
+
+build7627a() {
+  export MACHINE=msm7627a
+  cdbitbake msm-x11-image
+}
+
+build8960() {
+  export MACHINE=msm8960
+  cdbitbake msm-x11-image
+}
+
+buildperf8960() {
+  export MACHINE=msm8960-perf
+  cdbitbake msm-x11-image
+}
+
+buildboth8960() {
+  build8960 && \
+  buildperf8960
+}
+
+buildperf8974() {
+  export MACHINE=msm8974-perf
+  cdbitbake msm-x11-image
+}
+
+buildclean() {
+  set -x
+  cd ${WS}/oe-core/build
+  rm -rf bitbake.lock pseudodone sstate-cache tmp-eglibc && cd - || cd -
+  set +x
+}
+
+cdbitbake() {
+  cd ${WS}/oe-core/build
+  bitbake $@ && cd - || cd -
+}
+
+# Yocto/OE-core works a bit differently than OE-classic so we're
+# going to source the OE build environment setup script they provided.  
+# This will dump the user in ${WS}/yocto/build, ready to run the 
+# convienence function or straight up bitbake commands.
+. ${WS}/oe-core/oe-init-build-env
+
+# oe-init-build-env calls oe-buildenv-internal which sets
+# BB_ENV_EXTRAWHITE, append our vars to the list
+export BB_ENV_EXTRAWHITE="${BB_ENV_EXTRAWHITE} DL_DIR"