diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..6678c81 --- /dev/null +++ b/.gitignore @@ -0,0 +1,2 @@ +build/ +vscode-bitbake-build/ diff --git a/.gitmodules b/.gitmodules new file mode 100644 index 0000000..963d079 --- /dev/null +++ b/.gitmodules @@ -0,0 +1,8 @@ +[submodule "bitbake"] + path = bitbake + url = ssh://git@bitbucket.gad.local:7999/ico/bitbake.git + branch = 2.0 +[submodule "layers/openembedded-core"] + path = layers/openembedded-core + url = ssh://git@bitbucket.gad.local:7999/ico/openembedded-core.git + branch = kirkstone diff --git a/bitbake b/bitbake new file mode 160000 index 0000000..ac576d6 --- /dev/null +++ b/bitbake @@ -0,0 +1 @@ +Subproject commit ac576d6fad6bba0cfea931883f25264ea83747ca diff --git a/layers/meta-belden-coreos/README b/layers/meta-belden-coreos/README new file mode 100644 index 0000000..6cb9caf --- /dev/null +++ b/layers/meta-belden-coreos/README @@ -0,0 +1,41 @@ +This README file contains information on the contents of the meta-belden-coreos layer. + +Please see the corresponding sections below for details. + +Dependencies +============ + + URI: + branch: + + URI: + branch: + + . + . + . + +Patches +======= + +Please submit any patches against the meta-belden-coreos layer to the xxxx mailing list (xxxx@zzzz.org) +and cc: the maintainer: + +Maintainer: XXX YYYYYY + +Table of Contents +================= + + I. Adding the meta-belden-coreos layer to your build + II. Misc + + +I. Adding the meta-belden-coreos layer to your build +================================================= + +Run 'bitbake-layers add-layer meta-belden-coreos' + +II. Misc +======== + +--- replace with specific information about the meta-belden-coreos layer --- diff --git a/layers/meta-belden-coreos/conf/layer.conf b/layers/meta-belden-coreos/conf/layer.conf new file mode 100644 index 0000000..7365b7a --- /dev/null +++ b/layers/meta-belden-coreos/conf/layer.conf @@ -0,0 +1,13 @@ +# We have a conf and classes directory, add to BBPATH +BBPATH .= ":${LAYERDIR}" + +# We have recipes-* directories, add to BBFILES +BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \ + ${LAYERDIR}/recipes-*/*/*.bbappend" + +BBFILE_COLLECTIONS += "meta-belden-coreos" +BBFILE_PATTERN_meta-belden-coreos = "^${LAYERDIR}/" +BBFILE_PRIORITY_meta-belden-coreos = "6" + +LAYERDEPENDS_meta-belden-coreos = "core" +LAYERSERIES_COMPAT_meta-belden-coreos = "kirkstone" diff --git a/layers/meta-belden-coreos/recipes-example/example/example_0.1.bb b/layers/meta-belden-coreos/recipes-example/example/example_0.1.bb new file mode 100644 index 0000000..facaae3 --- /dev/null +++ b/layers/meta-belden-coreos/recipes-example/example/example_0.1.bb @@ -0,0 +1,13 @@ +SUMMARY = "bitbake-layers recipe" +DESCRIPTION = "Recipe created by bitbake-layers" +LICENSE = "MIT" + +python do_display_banner() { + bb.plain("***********************************************"); + bb.plain("* *"); + bb.plain("* Example recipe created by bitbake-layers *"); + bb.plain("* *"); + bb.plain("***********************************************"); +} + +addtask display_banner before do_build diff --git a/layers/openembedded-core b/layers/openembedded-core new file mode 160000 index 0000000..f7766da --- /dev/null +++ b/layers/openembedded-core @@ -0,0 +1 @@ +Subproject commit f7766da462905ec67bf549d46b8017be36cd5b2a diff --git a/oe-init-build-env b/oe-init-build-env new file mode 100755 index 0000000..a6b2ca3 --- /dev/null +++ b/oe-init-build-env @@ -0,0 +1,44 @@ +#!/bin/sh + +# This script is used to setup the OE Build Envrionment +# Normally this is called as '. ./oe-init-build-env ' + +# On some shell, we can get the path of this script when sources. Otherwise we +# use the current directory as a fallback +if [ -n "$BASH_SOURCE" ]; then + CORE_OS_ROOT=$(dirname "$BASH_SOURCE") +elif [ -n "$ZSH_NAME" ]; then + CORE_OS_ROOT=$(dirname "$0") +else + CORE_OS_ROOT="$(pwd)" +fi + +# Get a non relative path to the root directory +CORE_OS_ROOT=$(readlink -f "${CORE_OS_ROOT}") + +# Set the path to bitbake, openembedded-core and the template directory +BITBAKEDIR="${CORE_OS_ROOT}/bitbake" +OEROOT="${CORE_OS_ROOT}/layers/openembedded-core" +TEMPLATECONF="${CORE_OS_ROOT}/templates" + +# Sanity checks + +# This check detect if CORE_OS_ROOT is valid, by checking if the templates +# directory exists. Usefull has we use $(pwd) as a fallback method on some shell +if [ ! -d "$TEMPLATECONF" ]; then + echo "Error: $TEMPLATECONF doesn't exist!" >&2 + echo "Please run this script in oe-init-build-env's directory." >&2 + return 1 +fi + +# This check detect if BITBAKEDIR exist. It's a simple way to check that we have +# fetched our git submodules +if [ ! -d "$BITBAKEDIR" ]; then + echo "Error: $BITBAKEDIR doesn't exist!" >&2 + echo "Please ensure all git submodule are fetched." >&2 + return 1 +fi + +# Call the oe-init-build-env scripts of openembedded-core +. "${OEROOT}/oe-init-build-env" "${1:-$CORE_OS_ROOT/build}" + diff --git a/templates/bblayers.conf.sample b/templates/bblayers.conf.sample new file mode 100644 index 0000000..e406de5 --- /dev/null +++ b/templates/bblayers.conf.sample @@ -0,0 +1,11 @@ +# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf +# changes incompatibly +LCONF_VERSION = "7" + +BBPATH = "${TOPDIR}" +BBFILES ?= "" + +BBLAYERS ?= " \ + ##OEROOT##/meta \ + ##OEROOT##/../meta-belden-coreos \ + " diff --git a/templates/conf-notes.txt b/templates/conf-notes.txt new file mode 100644 index 0000000..90cb2d3 --- /dev/null +++ b/templates/conf-notes.txt @@ -0,0 +1,23 @@ + ____ _ _ _____ ____ _____ + | _ \ | | | | / ____| / __ \ / ____| + | |_) | ___| | __| | ___ _ __ | | ___ _ __ ___| | | | (___ + | _ < / _ \ |/ _` |/ _ \ '_ \ | | / _ \| '__/ _ \ | | |\___ \ + | |_) | __/ | (_| | __/ | | | | |___| (_) | | | __/ |__| |____) | + |____/ \___|_|\__,_|\___|_| |_| \_____\___/|_| \___|\____/|_____/ + +### Shell environment set up for builds. ### + +You can now run 'bitbake ' + +Common targets are: + core-image-minimal + core-image-full-cmdline + meta-toolchain + meta-ide-support + +You can also run generated qemu images with a command like 'runqemu qemuarm64'. + +Other commonly useful commands are: + - 'devtool' and 'recipetool' handle common recipe tasks + - 'bitbake-layers' handles common layer tasks + - 'oe-pkgdata-util' handles common target package tasks diff --git a/templates/local.conf.sample b/templates/local.conf.sample new file mode 100644 index 0000000..795c944 --- /dev/null +++ b/templates/local.conf.sample @@ -0,0 +1,239 @@ +# +# 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.sample.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 qemuarm64 if no other machine is selected: +MACHINE ??= "qemuarm64" + +# +# 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 target architecture +# +# This variable specifies the architecture to build SDK 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, x86_64, aarch64 +#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) +# "src-pkgs" - add -src packages for all installed packages +# (adds source code for debugging) +# "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 +USER_CLASSES ?= "buildstats" + + +# +# 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. It can also +# run tests against any SDK that are built. To enable this uncomment these lines. +# See classes/test{image,sdk}.bbclass for further details. +#IMAGE_CLASSES += "testimage testsdk" +#TESTIMAGE_AUTO:qemuall = "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 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" + +# +# 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 than 100MB or 1K inodes, perform a hard halt +# 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 necessary to monitor /tmp, if there is no space left the build will fail +# with very exotic errors. +BB_DISKMON_DIRS ??= "\ + STOPTASKS,${TMPDIR},1G,100K \ + STOPTASKS,${DL_DIR},1G,100K \ + STOPTASKS,${SSTATE_DIR},1G,100K \ + STOPTASKS,/tmp,100M,100K \ + HALT,${TMPDIR},100M,1K \ + HALT,${DL_DIR},100M,1K \ + HALT,${SSTATE_DIR},100M,1K \ + HALT,/tmp,10M,1K" + +# +# Shared-state files from other locations +# +# As mentioned above, shared state files are prebuilt cache data objects which can be +# 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 https 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://.* https://someserver.tld/share/sstate/PATH;downloadfilename=PATH \ +#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 libsdl2-native will +# be built, if you want to use your host's libSDL instead of the minimal libsdl built +# by libsdl2-native then uncomment the ASSUME_PROVIDED line below. +PACKAGECONFIG:append:pn-qemu-system-native = " sdl" +PACKAGECONFIG:append:pn-nativesdk-qemu = " sdl" +#ASSUME_PROVIDED += "libsdl2-native" + +# +# Hash Equivalence +# +# Enable support for automatically running a local hash equivalence server and +# instruct bitbake to use a hash equivalence aware signature generator. Hash +# equivalence improves reuse of sstate by detecting when a given sstate +# artifact can be reused as equivalent, even if the current task hash doesn't +# match the one that generated the artifact. +# +# A shared hash equivalent server can be set with ":" format +# +#BB_HASHSERVE = "auto" +#BB_SIGNATURE_HANDLER = "OEEquivHash" + +# +# Memory Resident Bitbake +# +# Bitbake's server component can stay in memory after the UI for the current command +# has completed. This means subsequent commands can run faster since there is no need +# for bitbake to reload cache files and so on. Number is in seconds, after which the +# server will shut down. +# +#BB_SERVER_TIMEOUT = "60" + +# 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 = "2"