On Thu, Dec 12, 2024 at 06:00:02PM +0530, Chirag Shilwant via
lists.yoctoproject.org wrote:
> From: Telukula Jeevan Kumar Sahu <[email protected]>
>
> - Add processor-sdk-09.03.05.02-legacy-config.txt used for building AM335x,
> AM437x, AM65x.
>
> Signed-off-by: Telukula Jeevan Kumar Sahu <[email protected]>
> Signed-off-by: Chirag Shilwant <[email protected]>
> ---
> ...ocessor-sdk-09.03.05.02-legacy-config.json | 125 +++++++++++++
> .../bblayers.conf.sample | 31 ++++
> .../conf-notes.txt | 22 +++
> .../conf-summary.txt | 1 +
> .../local.conf.sample | 175 ++++++++++++++++++
> ...rocessor-sdk-09.03.05.02-legacy-config.txt | 16 ++
> ...rocessor-sdk-09.03.05.02-legacy-config.yml | 69 +++++++
> ...rocessor-sdk-09.03.05.02-legacy-config.xml | 63 +++++++
> 8 files changed, 502 insertions(+)
> create mode 100644
> bitbake-setup/processor-sdk_processor-sdk-09.03.05.02-legacy-config.json
> create mode 100644
> conf/templates/processor-sdk_processor-sdk-09.03.05.02-legacy-config/bblayers.conf.sample
> create mode 100644
> conf/templates/processor-sdk_processor-sdk-09.03.05.02-legacy-config/conf-notes.txt
> create mode 100644
> conf/templates/processor-sdk_processor-sdk-09.03.05.02-legacy-config/conf-summary.txt
> create mode 100644
> conf/templates/processor-sdk_processor-sdk-09.03.05.02-legacy-config/local.conf.sample
> create mode 100644
> configs/processor-sdk/processor-sdk-09.03.05.02-legacy-config.txt
> create mode 100644
> kas/processor-sdk/processor-sdk-09.03.05.02-legacy-config.yml
> create mode 100644
> src/configs/processor-sdk/processor-sdk-09.03.05.02-legacy-config.xml
>
> diff --git
> a/bitbake-setup/processor-sdk_processor-sdk-09.03.05.02-legacy-config.json
> b/bitbake-setup/processor-sdk_processor-sdk-09.03.05.02-legacy-config.json
> new file mode 100644
> index 0000000..08ff325
> --- /dev/null
> +++ b/bitbake-setup/processor-sdk_processor-sdk-09.03.05.02-legacy-config.json
> @@ -0,0 +1,125 @@
> +{
> + "version": "1.0",
> + "description": "TI Processor SDK v09.03.05.02-legacy",
> + "sources": {
> + "oe-layersetup": {
> + "git-remote": {
> + "remotes": {
> + "origin": {
> + "uri": "https://git.ti.com/git/arago-project/oe-layersetup.git";
> + }
> + },
> + "rev": "wip"
Why wip? Should it be master?
> + },
> + "path": "oe-layersetup"
> + },
> + "bitbake": {
> + "git-remote": {
> + "remotes": {
> + "origin": {
> + "uri": "https://git.openembedded.org/bitbake";
> + }
> + },
> + "rev": "2.0"
> + },
> + "path": "bitbake"
> + },
> + "meta-tisdk": {
> + "git-remote": {
> + "remotes": {
> + "origin": {
> + "uri": "https://github.com/TexasInstruments/meta-tisdk.git";
> + }
> + },
> + "rev": "kirkstone"
> + },
> + "path": "meta-tisdk"
> + },
> + "meta-arago": {
> + "git-remote": {
> + "remotes": {
> + "origin": {
> + "uri": "https://git.yoctoproject.org/meta-arago";
> + }
> + },
> + "rev": "kirkstone"
> + },
> + "path": "meta-arago"
> + },
> + "meta-qt5": {
> + "git-remote": {
> + "remotes": {
> + "origin": {
> + "uri": "https://github.com/meta-qt5/meta-qt5.git";
> + }
> + },
> + "rev": "kirkstone"
> + },
> + "path": "meta-qt5"
> + },
> + "meta-virtualization": {
> + "git-remote": {
> + "remotes": {
> + "origin": {
> + "uri": "https://git.yoctoproject.org/meta-virtualization";
> + }
> + },
> + "rev": "kirkstone"
> + },
> + "path": "meta-virtualization"
> + },
> + "meta-openembedded": {
> + "git-remote": {
> + "remotes": {
> + "origin": {
> + "uri": "https://git.openembedded.org/meta-openembedded";
> + }
> + },
> + "rev": "kirkstone"
> + },
> + "path": "meta-openembedded"
> + },
> + "meta-ti": {
> + "git-remote": {
> + "remotes": {
> + "origin": {
> + "uri": "https://git.yoctoproject.org/meta-ti";
> + }
> + },
> + "rev": "kirkstone"
> + },
> + "path": "meta-ti"
> + },
> + "meta-arm": {
> + "git-remote": {
> + "remotes": {
> + "origin": {
> + "uri": "https://git.yoctoproject.org/meta-arm";
> + }
> + },
> + "rev": "kirkstone"
> + },
> + "path": "meta-arm"
> + },
> + "oe-core": {
> + "git-remote": {
> + "remotes": {
> + "origin": {
> + "uri": "https://git.openembedded.org/openembedded-core";
> + }
> + },
> + "rev": "kirkstone"
> + },
> + "path": "oe-core"
> + }
> + },
> + "configuration": {
> + "bitbake-setup": {
> + "default": {
> + "description": "Default build configuration",
> + "template":
> "oe-layersetup-processor-sdk_processor-sdk-09.03.05.02-legacy-config",
> + "targets": [ "bitbake -k tisdk-default-image" ]
> + }
> + }
> + }
> +}
> diff --git
> a/conf/templates/processor-sdk_processor-sdk-09.03.05.02-legacy-config/bblayers.conf.sample
>
> b/conf/templates/processor-sdk_processor-sdk-09.03.05.02-legacy-config/bblayers.conf.sample
> new file mode 100644
> index 0000000..a888c1c
> --- /dev/null
> +++
> b/conf/templates/processor-sdk_processor-sdk-09.03.05.02-legacy-config/bblayers.conf.sample
> @@ -0,0 +1,31 @@
> +# This template file was created by taking the
> oe-core/meta/conf/bblayers.conf
> +# file and removing the BBLAYERS section at the end.
> +
> +# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
> +# changes incompatibly
> +LCONF_VERSION = "5"
> +
> +BBPATH = "${TOPDIR}"
> +BBFILES ?= ""
> +
> +BBLAYERS ?= " \
> + ##OEROOT##/../meta-tisdk
> + ##OEROOT##/../meta-arago/meta-arago-distro
> + ##OEROOT##/../meta-arago/meta-arago-extras
> + ##OEROOT##/../meta-arago/meta-arago-demos
> + ##OEROOT##/../meta-arago/meta-arago-test
> + ##OEROOT##/../meta-qt5
> + ##OEROOT##/../meta-virtualization
> + ##OEROOT##/../meta-openembedded/meta-networking
> + ##OEROOT##/../meta-openembedded/meta-python
> + ##OEROOT##/../meta-openembedded/meta-oe
> + ##OEROOT##/../meta-openembedded/meta-gnome
> + ##OEROOT##/../meta-openembedded/meta-filesystems
> + ##OEROOT##/../meta-openembedded/meta-multimedia
> + ##OEROOT##/../meta-ti/meta-ti-extras
> + ##OEROOT##/../meta-ti/meta-ti-bsp
> + ##OEROOT##/../meta-arm/meta-arm
> + ##OEROOT##/../meta-arm/meta-arm-toolchain
> + ##OEROOT##/../oe-core/meta
> + ##OEROOT##/../oe-layersetup
> +"
> diff --git
> a/conf/templates/processor-sdk_processor-sdk-09.03.05.02-legacy-config/conf-notes.txt
>
> b/conf/templates/processor-sdk_processor-sdk-09.03.05.02-legacy-config/conf-notes.txt
> new file mode 100644
> index 0000000..1880460
> --- /dev/null
> +++
> b/conf/templates/processor-sdk_processor-sdk-09.03.05.02-legacy-config/conf-notes.txt
> @@ -0,0 +1,22 @@
> +
> +### Shell environment set up for builds. ###
> +
> +You can now run 'bitbake <target>'
> +
> +If you have not set MACHINE in your local.conf you can run
> +'MACHINE=xxxxx bitbake <target>'
> +
> +Common targets are:
> + tisdk-default-image
> + tisdk-base-image
> + tisdk-bootstrap-base-image
> + tisdk-bootstrap-image
> + tisdk-thinlinux-image
> + tisdk-tiny-image
> +
> +You can also run generated qemu images with a command like 'runqemu
> qemux86-64'.
> +
> +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/conf/templates/processor-sdk_processor-sdk-09.03.05.02-legacy-config/conf-summary.txt
>
> b/conf/templates/processor-sdk_processor-sdk-09.03.05.02-legacy-config/conf-summary.txt
> new file mode 100644
> index 0000000..5d87e2e
> --- /dev/null
> +++
> b/conf/templates/processor-sdk_processor-sdk-09.03.05.02-legacy-config/conf-summary.txt
> @@ -0,0 +1 @@
> +TI Processor SDK v09.03.05.02-legacy
> diff --git
> a/conf/templates/processor-sdk_processor-sdk-09.03.05.02-legacy-config/local.conf.sample
>
> b/conf/templates/processor-sdk_processor-sdk-09.03.05.02-legacy-config/local.conf.sample
> new file mode 100644
> index 0000000..7575b4b
> --- /dev/null
> +++
> b/conf/templates/processor-sdk_processor-sdk-09.03.05.02-legacy-config/local.conf.sample
> @@ -0,0 +1,175 @@
> +# CONF_VERSION is increased each time build/conf/ changes incompatibly
> +CONF_VERSION = "2"
> +
> +#
> +# 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.
> +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).
> +SSTATE_DIR = "${TOPDIR}/build/sstate-cache"
> +
> +#
> +# 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 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/"
> +
> +#
> +# 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.
> +TMPDIR = "${TOPDIR}/arago-tmp"
> +
> +# By default, DEPLOY_DIR is inside TMPDIR, but can be changed here to be
> outside
> +#DEPLOY_DIR = "${TOPDIR}/deploy"
> +
> +#
> +# 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 ?= "arago"
> +
> +#
> +# 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 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 ?= "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)
> +# "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 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-swab' to perform host system intrusion detection
> +# NOTE: mklibs also needs to be explicitly enabled for a given image, see
> local.conf.extended
> +USER_CLASSES ?= "buildstats"
> +
> +# By default disable interactive patch resolution (tasks will just fail
> instead):
> +PATCHRESOLVE = "noop"
> +
> +# By default the machine configuration file sets the IMAGE_FSTYPES. But if
> you
> +# would like to add additional file system types you can uncomment the
> +# following line and add the additional IMAGE_FSTYPES you want created
> +# as part of the build flow. Some common types are listed below and you
> +# can remove the ones you do not want.
> +# IMAGE_FSTYPES += "jffs2 cramfs ext2.gz ext3.gz squashfs ubi tar.gz tar.bz2
> cpio"
> +
> +#
> +# 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 ?= "1"
> +#
> +# The second option controls how many processes make should run in parallel
> when
> +# running compile tasks:
> +#
> +# PARALLEL_MAKE ?= "-j 1"
> +#
> +# For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4"
> would
> +# be appropriate for example
> +#
> +# NOTE: By default, bitbake will choose the number of processeors on your
> host
> +# so you should not need to set this unless you are wanting to lower the
> number
> +# allowed.
> +#
> +
> +DISTRO = "arago"
> +
> +# Set terminal types by default it expects gnome-terminal
> +# but we chose xterm
> +TERMCMD = "${XTERM_TERMCMD}"
> +TERMCMDRUN = "${XTERM_TERMCMDRUN}"
> +
> +# Don't generate the mirror tarball for SCM repos, the snapshot is enough
> +BB_GENERATE_MIRROR_TARBALLS = "0"
> +
> +# Uncomment this to remove work directory after packaging to save disk space
> +#INHERIT += "rm_work"
> +
> +# Keep one set of images by default
> +RM_OLD_IMAGE = "1"
> +
> +# Enable local PR service for binary feeds
> +PRSERV_HOST = "localhost:0"
> +
> +# Enable hash equiv server
> +BB_SIGNATURE_HANDLER = "OEEquivHash"
> +BB_HASHSERVE = "auto"
> +
> +# It is recommended to activate "buildhistory" for testing the PR service
> +INHERIT += "buildhistory"
> +BUILDHISTORY_COMMIT = "1"
> diff --git
> a/configs/processor-sdk/processor-sdk-09.03.05.02-legacy-config.txt
> b/configs/processor-sdk/processor-sdk-09.03.05.02-legacy-config.txt
> new file mode 100644
> index 0000000..d3ef62d
> --- /dev/null
> +++ b/configs/processor-sdk/processor-sdk-09.03.05.02-legacy-config.txt
> @@ -0,0 +1,16 @@
> +# This file takes repo entries in the format
> +# repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern]
> +
> +bitbake,https://git.openembedded.org/bitbake,2.0,3f88b005244a0afb5d5c7260e54a94a453ec9b3e
> +meta-tisdk,https://github.com/TexasInstruments/meta-tisdk.git,kirkstone,09.03.05.02,layers=
> +meta-arago,https://git.yoctoproject.org/meta-arago,kirkstone,09.03.05,layers=meta-arago-distro:meta-arago-extras:meta-arago-demos:meta-arago-test
> +meta-qt5,https://github.com/meta-qt5/meta-qt5.git,kirkstone,644ebf220245bdc06e7696ccc90acc97a0dd2566,layers=
> +meta-virtualization,https://git.yoctoproject.org/meta-virtualization,kirkstone,460ea78d7f8d5d16799d0b7334b95d8170c9e338,layers=
> +meta-openembedded,https://git.openembedded.org/meta-openembedded,kirkstone,4ad41baed6236d499804cbfc4f174042d84fce97,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems:meta-multimedia
> +meta-ti,https://git.yoctoproject.org/meta-ti,kirkstone,09.03.05,layers=meta-ti-extras:meta-ti-bsp
> +meta-arm,https://git.yoctoproject.org/meta-arm,kirkstone,936c02ec13661bd86a05f7f90e1b920d5092d670,layers=meta-arm:meta-arm-toolchain
> +oe-core,https://git.openembedded.org/openembedded-core,kirkstone,e42b6a40a3a01e328966bb5ee1bb3e0993975b15,layers=meta
> +
> +OECORELAYERCONF=./sample-files/bblayers.conf.sample
> +OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
> +BITBAKE_INCLUSIVE_VARS=yes
> diff --git a/kas/processor-sdk/processor-sdk-09.03.05.02-legacy-config.yml
> b/kas/processor-sdk/processor-sdk-09.03.05.02-legacy-config.yml
> new file mode 100644
> index 0000000..e3bb5b1
> --- /dev/null
> +++ b/kas/processor-sdk/processor-sdk-09.03.05.02-legacy-config.yml
> @@ -0,0 +1,69 @@
> +header:
> + version: 17
> + includes:
> + - ../templates/bblayers.conf.yml
> + - ../templates/local-arago64-v2.conf.yml
> +
> +target: tisdk-default-image
> +
> +repos:
> + meta-tisdk:
> + url: "https://github.com/TexasInstruments/meta-tisdk.git";
> + branch: "kirkstone"
> + commit: "09.03.05.02"
> +
> + meta-arago:
> + url: "https://git.yoctoproject.org/meta-arago";
> + branch: "kirkstone"
> + commit: "09.03.05"
> + layers:
> + meta-arago-distro:
> + meta-arago-extras:
> + meta-arago-demos:
> + meta-arago-test:
> +
> + meta-qt5:
> + url: "https://github.com/meta-qt5/meta-qt5.git";
> + branch: "kirkstone"
> + commit: "644ebf220245bdc06e7696ccc90acc97a0dd2566"
> +
> + meta-virtualization:
> + url: "https://git.yoctoproject.org/meta-virtualization";
> + branch: "kirkstone"
> + commit: "460ea78d7f8d5d16799d0b7334b95d8170c9e338"
> +
> + meta-openembedded:
> + url: "https://git.openembedded.org/meta-openembedded";
> + branch: "kirkstone"
> + commit: "4ad41baed6236d499804cbfc4f174042d84fce97"
> + layers:
> + meta-networking:
> + meta-python:
> + meta-oe:
> + meta-gnome:
> + meta-filesystems:
> + meta-multimedia:
> +
> + meta-ti:
> + url: "https://git.yoctoproject.org/meta-ti";
> + branch: "kirkstone"
> + commit: "09.03.05"
> + layers:
> + meta-ti-extras:
> + meta-ti-bsp:
> +
> + meta-arm:
> + url: "https://git.yoctoproject.org/meta-arm";
> + branch: "kirkstone"
> + commit: "936c02ec13661bd86a05f7f90e1b920d5092d670"
> + layers:
> + meta-arm:
> + meta-arm-toolchain:
> +
> + oe-core:
> + url: "https://git.openembedded.org/openembedded-core";
> + branch: "kirkstone"
> + commit: "e42b6a40a3a01e328966bb5ee1bb3e0993975b15"
> + layers:
> + meta:
> +
> diff --git
> a/src/configs/processor-sdk/processor-sdk-09.03.05.02-legacy-config.xml
> b/src/configs/processor-sdk/processor-sdk-09.03.05.02-legacy-config.xml
> new file mode 100644
> index 0000000..71bd067
> --- /dev/null
> +++ b/src/configs/processor-sdk/processor-sdk-09.03.05.02-legacy-config.xml
> @@ -0,0 +1,63 @@
> +<?xml version='1.0'?>
> +<config>
> + <description>TI Processor SDK v09.03.05.02-legacy</description>
> +
> + <xi:include href='../../common/targets_arago.xml'
> xmlns:xi='http://www.w3.org/2001/XInclude'/>
> + <xi:include href='../../templates/bblayers.conf.xml'
> xmlns:xi='http://www.w3.org/2001/XInclude'/>
> + <xi:include href='../../templates/local-arago64-v2.conf.xml'
> xmlns:xi='http://www.w3.org/2001/XInclude'/>
> +
> + <bitbake url='https://git.openembedded.org/bitbake' branch='2.0'
> commit='3f88b005244a0afb5d5c7260e54a94a453ec9b3e'/>
> +
> + <repos>
> + <repo name='meta-tisdk'
> url='https://github.com/TexasInstruments/meta-tisdk.git' branch='kirkstone'
> commit='09.03.05.02'>
> + <layers/>
> + </repo>
> + <repo name='meta-arago'
> url='https://git.yoctoproject.org/meta-arago' branch='kirkstone'
> commit='09.03.05'>
> + <layers>
> + <layer>meta-arago-distro</layer>
> + <layer>meta-arago-extras</layer>
> + <layer>meta-arago-demos</layer>
> + <layer>meta-arago-test</layer>
> + </layers>
> + </repo>
> + <repo name='meta-qt5' url='https://github.com/meta-qt5/meta-qt5.git'
> branch='kirkstone' commit='644ebf220245bdc06e7696ccc90acc97a0dd2566'>
> + <layers/>
> + </repo>
> + <repo name='meta-virtualization'
> url='https://git.yoctoproject.org/meta-virtualization' branch='kirkstone'
> commit='460ea78d7f8d5d16799d0b7334b95d8170c9e338'>
> + <layers/>
> + </repo>
> + <repo name='meta-openembedded'
> url='https://git.openembedded.org/meta-openembedded' branch='kirkstone'
> commit='4ad41baed6236d499804cbfc4f174042d84fce97'>
> + <layers>
> + <layer>meta-networking</layer>
> + <layer>meta-python</layer>
> + <layer>meta-oe</layer>
> + <layer>meta-gnome</layer>
> + <layer>meta-filesystems</layer>
> + <layer>meta-multimedia</layer>
> + </layers>
> + </repo>
> + <repo name='meta-ti' url='https://git.yoctoproject.org/meta-ti'
> branch='kirkstone' commit='09.03.05'>
> + <layers>
> + <layer>meta-ti-extras</layer>
> + <layer>meta-ti-bsp</layer>
> + </layers>
> + </repo>
> + <repo name='meta-arm' url='https://git.yoctoproject.org/meta-arm'
> branch='kirkstone' commit='936c02ec13661bd86a05f7f90e1b920d5092d670'>
> + <layers>
> + <layer>meta-arm</layer>
> + <layer>meta-arm-toolchain</layer>
> + </layers>
> + </repo>
> + <repo name='oe-core'
> url='https://git.openembedded.org/openembedded-core' branch='kirkstone'
> commit='e42b6a40a3a01e328966bb5ee1bb3e0993975b15'>
> + <layers>
> + <layer>meta</layer>
> + </layers>
> + </repo>
> + </repos>
> +
> + <tools>
> + <tool type='oe-layersetup'>
> + <var name='BITBAKE_INCLUSIVE_VARS' value='yes'/>
> + </tool>
> + </tools>
> +</config>
> --
> 2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#15659):
https://lists.yoctoproject.org/g/meta-arago/message/15659
Mute This Topic: https://lists.yoctoproject.org/mt/110078592/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-arago/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
