Initial NWL Commit ...
Signed-off-by: Patrick Zysset <patrick.zysset@netmodule.com>
This commit is contained in:
Patrick Zysset
commit
c11d0a5044
|
|
@ -0,0 +1,6 @@
|
|||
build/
|
||||
vscode-bitbake-build/
|
||||
documentation/_build/
|
||||
documentation/oe-logs
|
||||
documentation/oe-workdir
|
||||
__pycache__
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
[submodule "layers/coreos"]
|
||||
path = layers/coreos
|
||||
url = ssh://git@bitbucket.gad.local:7999/ico/coreos.git
|
||||
branch = master
|
||||
[submodule "coreos"]
|
||||
path = coreos
|
||||
url = ssh://git@bitbucket.gad.local:7999/ico/coreos.git
|
||||
branch = master
|
||||
|
|
@ -0,0 +1,4 @@
|
|||
NETMODULE WIRELESS LINUX
|
||||
------------------------
|
||||
*...a Belden Core-OS Distribution!*
|
||||
|
||||
|
|
@ -0,0 +1 @@
|
|||
Subproject commit bb4c4ec9f1d49aa277109aea414ee18cf4f291bb
|
||||
|
|
@ -0,0 +1,17 @@
|
|||
Permission is hereby granted, free of charge, to any person obtaining a copy
|
||||
of this software and associated documentation files (the "Software"), to deal
|
||||
in the Software without restriction, including without limitation the rights
|
||||
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
||||
copies of the Software, and to permit persons to whom the Software is
|
||||
furnished to do so, subject to the following conditions:
|
||||
|
||||
The above copyright notice and this permission notice shall be included in
|
||||
all copies or substantial portions of the Software.
|
||||
|
||||
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
||||
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
||||
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
||||
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
||||
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
||||
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
||||
THE SOFTWARE.
|
||||
|
|
@ -0,0 +1,41 @@
|
|||
This README file contains information on the contents of the meta-nwl-distro layer.
|
||||
|
||||
Please see the corresponding sections below for details.
|
||||
|
||||
Dependencies
|
||||
============
|
||||
|
||||
URI: <first dependency>
|
||||
branch: <branch name>
|
||||
|
||||
URI: <second dependency>
|
||||
branch: <branch name>
|
||||
|
||||
.
|
||||
.
|
||||
.
|
||||
|
||||
Patches
|
||||
=======
|
||||
|
||||
Please submit any patches against the meta-nwl-distro layer to the xxxx mailing list (xxxx@zzzz.org)
|
||||
and cc: the maintainer:
|
||||
|
||||
Maintainer: XXX YYYYYY <xxx.yyyyyy@zzzzz.com>
|
||||
|
||||
Table of Contents
|
||||
=================
|
||||
|
||||
I. Adding the meta-nwl-distro layer to your build
|
||||
II. Misc
|
||||
|
||||
|
||||
I. Adding the meta-nwl-distro layer to your build
|
||||
=================================================
|
||||
|
||||
Run 'bitbake-layers add-layer meta-nwl-distro'
|
||||
|
||||
II. Misc
|
||||
========
|
||||
|
||||
--- replace with specific information about the meta-nwl-distro layer ---
|
||||
|
|
@ -0,0 +1,20 @@
|
|||
# This should come at the beginning of the file, to ensure that you use
|
||||
# CoreOS defaults
|
||||
require conf/distro/belden-coreos.conf
|
||||
|
||||
# This should always be set in your own configuration file, to not use the
|
||||
# values of CoreOS
|
||||
DISTRO = "nwl"
|
||||
DISTRO_NAME = "Netmodule Wireless Linux"
|
||||
MAINTAINER = "Netmodule Software Teams"
|
||||
|
||||
# You may want to add a version and a codename to your distro instead of
|
||||
# using the version and codename of CoreOS
|
||||
DISTRO_VERSION = "2023.03"
|
||||
DISTRO_CODENAME = "NWL 2023 Edition (DRAFT)"
|
||||
|
||||
# Here you can override settings from the CoreOS distro or from
|
||||
# OpenEmbedded-core. But keep in mind that the CoreOS team doesn't support
|
||||
# all the features of OpenEmbedded-Core. We have added some checks for some
|
||||
# of the settings that we don't allow to change or that we don't support.
|
||||
# See the coreos-sanity.bbclass file for more info.
|
||||
|
|
@ -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-nwl-distro"
|
||||
BBFILE_PATTERN_meta-nwl-distro = "^${LAYERDIR}/"
|
||||
BBFILE_PRIORITY_meta-nwl-distro = "6"
|
||||
|
||||
LAYERDEPENDS_meta-nwl-distro = "core"
|
||||
LAYERSERIES_COMPAT_meta-nwl-distro = "kirkstone"
|
||||
|
|
@ -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
|
||||
|
|
@ -0,0 +1,35 @@
|
|||
#!/bin/sh
|
||||
|
||||
# This script is used to setup the OE Build Environment
|
||||
# Normally this is called as '. ./nwl-init-build-env <builddir>'
|
||||
|
||||
# On some shell, we can get the path of this script when sources. Otherwise we
|
||||
# use the current directory as a fallback
|
||||
if [ -z "$PRODUCT_ROOT" ]; then
|
||||
if [ -n "$BASH_SOURCE" ]; then
|
||||
PRODUCT_ROOT=$(dirname "$BASH_SOURCE")
|
||||
elif [ -n "$ZSH_NAME" ]; then
|
||||
PRODUCT_ROOT=$(dirname "$0")
|
||||
else
|
||||
PRODUCT_ROOT="$(pwd)"
|
||||
fi
|
||||
fi
|
||||
|
||||
# Get a non relative path to the root directory
|
||||
PRODUCT_ROOT=$(readlink -f "${PRODUCT_ROOT}")
|
||||
|
||||
# CoreOS init settings
|
||||
COREOS_ROOT="${PRODUCT_ROOT}/coreos"
|
||||
TEMPLATECONF="${PRODUCT_ROOT}/templates"
|
||||
|
||||
# Call the coreos-init-build-env scripts of CoreOS
|
||||
. "${COREOS_ROOT}/coreos-init-build-env" "${1:-$PRODUCT_ROOT/build}"
|
||||
|
||||
# From here the scripts and functions defined by CoreOS and
|
||||
# OpenEmbedded-Core are available
|
||||
|
||||
# Add support for ##PRODUCTS_LAYERSDIR## inside of bblayer template
|
||||
coreos-bblayers-envsub PRODUCT_LAYERSDIR "${PRODUCT_ROOT}/layers"
|
||||
|
||||
# Add the scripts directory of the product to the path
|
||||
coreos_path_add "${PRODUCT_ROOT}/scripts"
|
||||
|
|
@ -0,0 +1,22 @@
|
|||
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
|
||||
# changes incompatibly
|
||||
LCONF_VERSION = "7"
|
||||
|
||||
BBPATH = "${TOPDIR}"
|
||||
BBFILES ?= ""
|
||||
|
||||
BBLAYERS ?= " \
|
||||
##OEROOT##/meta \
|
||||
##COREOS_LAYERSDIR##/meta-belden-coreos \
|
||||
##COREOS_LAYERSDIR##/meta-belden-coreos-bsp \
|
||||
##COREOS_LAYERSDIR##/meta-belden-coreos-demo \
|
||||
##COREOS_LAYERSDIR##/meta-belden-marvell-bsp \
|
||||
##COREOS_LAYERSDIR##/meta-openembedded/meta-oe \
|
||||
##COREOS_LAYERSDIR##/meta-openembedded/meta-networking \
|
||||
##COREOS_LAYERSDIR##/meta-openembedded/meta-filesystems \
|
||||
##COREOS_LAYERSDIR##/meta-openembedded/meta-python \
|
||||
##COREOS_LAYERSDIR##/meta-openembedded/meta-webserver \
|
||||
##COREOS_LAYERSDIR##/meta-virtualization \
|
||||
##COREOS_LAYERSDIR##/meta-efibootguard \
|
||||
##COREOS_LAYERSDIR##/meta-swupdate \
|
||||
"
|
||||
|
|
@ -0,0 +1,25 @@
|
|||
____ _ _ _____ ____ _____
|
||||
| _ \ | | | | / ____| / __ \ / ____|
|
||||
| |_) | ___| | __| | ___ _ __ | | ___ _ __ ___| | | | (___
|
||||
| _ < / _ \ |/ _` |/ _ \ '_ \ | | / _ \| '__/ _ \ | | |\___ \
|
||||
| |_) | __/ | (_| | __/ | | | | |___| (_) | | | __/ |__| |____) |
|
||||
|____/ \___|_|\__,_|\___|_| |_| \_____\___/|_| \___|\____/|_____/
|
||||
|
||||
### Shell environment set up for builds. ###
|
||||
|
||||
You can now run 'bitbake <target>'
|
||||
|
||||
Common targets are:
|
||||
coreos-image-minimal
|
||||
coreos-image-all-features
|
||||
coreos-image-demo
|
||||
|
||||
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
|
||||
- 'bitbake-getvar' query the value of a variable
|
||||
- 'oe-pkgdata-util' handles common target package tasks
|
||||
|
||||
You can open the CoreOS documentation by running the 'coreos-doc' command.
|
||||
|
|
@ -0,0 +1,211 @@
|
|||
#
|
||||
# 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"
|
||||
#MACHINE ?= "cn9130-cf-pro"
|
||||
#
|
||||
# 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"
|
||||
|
||||
#
|
||||
# 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 ?= "nwl"
|
||||
|
||||
#
|
||||
# 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://.* http://sstate.gad.local/PATH;downloadfilename=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"
|
||||
|
||||
#
|
||||
# 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"
|
||||
Loading…
Reference in New Issue