Commit 9529c3ec authored by Paul Barker's avatar Paul Barker Committed by Paul Barker

Import build directory

We no longer need to use a submodule for the build directory.
Signed-off-by: Paul Barker's avatarPaul Barker <>
parent ebbfaf17
[submodule "meta-oryx"]
path = meta-oryx
url =
[submodule "build"]
path = build
url =
[submodule "bitbake"]
path = bitbake
url = git://
Subproject commit 6ec20d789e202fb411a674c80ef7d5054ef39cd9
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
${ORYX_BASE}/openembedded-core/meta \
${ORYX_BASE}/meta-openembedded/meta-oe \
${ORYX_BASE}/meta-openembedded/meta-networking \
${ORYX_BASE}/meta-openembedded/meta-python \
${ORYX_BASE}/meta-openembedded/meta-filesystems \
${ORYX_BASE}/meta-virtualization \
${ORYX_BASE}/meta-raspberrypi \
${ORYX_BASE}/meta-yocto/meta-yocto-bsp \
${ORYX_BASE}/meta-oryx \
# 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.
# 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 ?= "qemuarm64"
#MACHINE ?= "qemumips"
#MACHINE ?= "qemumips64"
#MACHINE ?= "qemuppc"
#MACHINE ?= "qemux86"
#MACHINE ?= "qemux86-64"
# This sets the default machine to be qemux86 if no other machine is selected:
MACHINE ??= "qemux86"
# Where to place downloads
# 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 ?= "${TOPDIR}/downloads"
# 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.
# 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).
# 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 compilation 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"
# 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 ipk:
PACKAGE_CLASSES ?= "package_ipk"
# SDK/ADT target architecture
# This variable specifies 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 ?= "x86_64"
# 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)
# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages
# (useful if you want to run the package test suites)
# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)
# "tools-debug" - add debugging tools (gdb, strace)
# "eclipse-debug" - add Eclipse remote debugging support
# "tools-profile" - add profiling tools (oprofile, 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"
# 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
# image-prelink disabled for now due to issues with IFUNC symbol relocation
USER_CLASSES ?= "buildstats image-mklibs"
# 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. See classes/testimage(-auto).bbclass for
# further details.
# 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):
# Disk Space Monitoring during the build
# Monitor the disk space during the build. If there is less that 1GB of space or less
# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
# of the build. The reason for this is that running completely out of space can corrupt
# files and damages the build in ways which may not be easily recoverable.
# It's necesary to monitor /tmp, if there is no space left the build will fail
# with very exotic errors.
STOPTASKS,/tmp,100M,100K \
ABORT,${DL_DIR},100M,1K \
# 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.
#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
#file://.* file:///some/local/dir/sstate/PATH"
# Qemu configuration
# By default qemu will build with a builtin VNC server where graphical output can be
# seen. The two lines below enable the SDL backend too. By default libsdl-native will
# be built, if you want to use your host's libSDL instead of the minimal libsdl built
# by libsdl-native then uncomment the ASSUME_PROVIDED line below.
#PACKAGECONFIG_append_pn-qemu-native = " sdl"
#PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
#ASSUME_PROVIDED += "libsdl-native"
# 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.
DISTRO = "oryx"
# Generate mirror tarballs for sources fetched from version control systems.
# This helps us to create a full source mirror.
export ORYX_BASE=$(realpath $(dirname $BASH_SOURCE)/../..)
export TOPDIR="${ORYX_BASE}/build"
TCMODE all_proxy ftp_proxy ftps_proxy http_proxy https_proxy no_proxy \
export PATH="${ORYX_BASE}/openembedded-core/scripts:${ORYX_BASE}/bitbake/bin:${PATH}"
cd "${TOPDIR}"
#! /bin/bash
set -e
set -o pipefail
if [[ -z "$VERSION" ]]; then
# Run a really clean build to ensure that all necessary sources end up in the
# downloads directory
rm -rf downloads sstate-cache
do_oryx_full() {
./scripts/ -C -L -V $VERSION -M $MACHINE -A host
./scripts/ -C -L -V $VERSION -M $MACHINE -A host-test
./scripts/ -C -L -V $VERSION -M $MACHINE -S guest -A full-cmdline
./scripts/ -C -L -V $VERSION -M $MACHINE -S guest -A minimal
do_oryx_full qemux86
do_oryx_full raspberrypi3
do_oryx_full raspberrypi3-64
do_oryx_full beaglebone-yocto
# Sync the relevant files from the downloads directory into a "sources"
# directory
mkdir -p pub/$VERSION/downloads
find downloads -maxdepth 1 -type f -not -name *.done -exec ln -f {} pub/$VERSION/{} \;
mv pub/$VERSION/downloads pub/$VERSION/sources
# Capture bitbake and layers
git -C .. archive-all --prefix oryx-$VERSION/ build/pub/$VERSION/oryx-$VERSION.tar.xz
#! /usr/bin/env python3
import argparse
import glob
import os
import subprocess
import shutil
import sys
import tarfile
def get_subfolder(args):
return "%s/%s/%s/%s/" % (args.version, args.machine, args.system_profile, args.application_profile)
def run_build(args):
"""Run a build using the configuration given in the args namespace"""
% (args.version, args.machine, args.system_profile, args.application_profile))
os.environ['ORYX_VERSION'] = args.version
os.environ['MACHINE'] = args.machine
os.environ['ORYX_SYSTEM_PROFILE'] = args.system_profile
os.environ['ORYX_APPLICATION_PROFILE'] = args.application_profile
subfolder = get_subfolder(args)
bitbake_status ="bitbake oryx-publish", shell=True)
# Copy the contents of the output files out of the tmp folder. The
# destination folder must not already exist for copytree to work.
folder = "tmp/deploy/oryx/" + subfolder
newfolder = "pub/" + subfolder
if os.path.exists(newfolder):
if os.path.exists(folder):
shutil.copytree(folder, newfolder)
# At least create an empty folder in case we need to create a FAILED
# file
# Create FAILED file if bitbake failed
if bitbake_status != 0:
failedfile = "%s/FAILED" % (newfolder)
return bitbake_status
def capture_logs(args):
"""Capture log files and archive them"""
directorylist = ['tmp/work/*/*/*/temp/run.*', 'tmp/work/*/*/*/temp/log.*', 'tmp/log/*']
globlist = []
for directory in directorylist:
for filename in glob.iglob(directory):
subfolder = get_subfolder(args)
tarlocation = "pub/%s/logs.tar.gz" % (subfolder)
tar =, "w:gz")
for item in globlist:
def parse_args():
"""Parse command line arguments into an args namespace"""
parser = argparse.ArgumentParser(
description="Build script for Oryx Embedded Linux"
parser.add_argument("-V", dest="version", metavar="VERSION", default="dev",
help="Version string used to identify this build")
parser.add_argument("-S", dest="system_profile", metavar="SYSTEM_PROFILE", default="native",
help="System profile selection")
parser.add_argument("-A", dest="application_profile", metavar="APPLICATION_PROFILE", default="minimal",
help="Application profile selection")
parser.add_argument("-M", dest="machine", metavar="MACHINE", default="qemux86",
help="Machine selection")
parser.add_argument("-C", "--clean", help="Performs a clean build", action="store_true")
parser.add_argument("-L", "--logs", help="Captures and archives log files", action="store_true")
return parser.parse_args()
def main():
args = parse_args()
if args.clean and os.path.exists("tmp"):
print(">>> Cleaning")
exitcode = run_build(args)
if args.logs:
print(">>> Capturing logs")
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment