StarlingX layer for OpenEmbedded build system
Go to file
Saul Wold 467e56bfdc Restructure STX Flock recipes
Create a new layer to manage the StarlingX Flock specific recipes

Signed-off-by: Saul Wold <sgw@linux.intel.com>
2020-05-17 16:00:29 -07:00
meta-stx-cloud/conf meta-stx-cloud: create layer and add layer.conf file 2020-05-17 16:00:29 -07:00
meta-stx-distro STX Images and Packagegroups 2020-05-17 16:00:29 -07:00
meta-stx-flock Restructure STX Flock recipes 2020-05-17 16:00:29 -07:00
meta-stx-integ/conf meta-stx-integ: create layer and add layer.conf file 2020-05-17 16:00:29 -07:00
meta-stx-virt/conf meta-stx-virt: create layer and add layer.conf file 2020-05-17 16:00:29 -07:00
recipes-bsp/grub Add copyright message to recipes 2020-04-20 13:07:41 -07:00
recipes-connectivity Move openssl10 bbappend to stak-common 2020-04-21 13:02:18 -07:00
recipes-containers Update docker-distribution_git.bb 2020-05-12 13:02:32 -07:00
recipes-core move stx specifics bb files to rescipes-stx 2020-05-13 12:54:08 -07:00
recipes-daemons/lldpd Add copyright message to recipes 2020-04-20 13:07:41 -07:00
recipes-dbs/mysql Layer cleanup: remove obsolete recipes and patches 2020-04-20 13:14:00 -07:00
recipes-devtools Move commone recipes and classes to meta-stak-common 2020-04-20 13:15:29 -07:00
recipes-extended Move commone recipes and classes to meta-stak-common 2020-04-20 13:15:29 -07:00
recipes-graphics/mesa Add copyright message to recipes 2020-04-20 13:07:41 -07:00
recipes-httpd Add copyright message to recipes 2020-04-20 13:07:41 -07:00
recipes-kernel/linux Add copyright message to recipes 2020-04-20 13:07:41 -07:00
recipes-networking Add copyright message to recipes 2020-04-20 13:07:41 -07:00
recipes-security/gssproxy Add copyright message to recipes 2020-04-20 13:07:41 -07:00
recipes-support Move commone recipes and classes to meta-stak-common 2020-04-20 13:15:29 -07:00
recipes-upstream/python Add copyright message to recipes 2020-04-20 13:07:41 -07:00
.gitignore Adding gitignore 2019-11-02 20:27:35 -07:00
LICENSE meta-stx: Add Apache-2.0 license 2020-04-20 13:16:21 -07:00
README.md Update README.md 2020-04-23 14:55:24 -07:00

meta-stx

Build

git clone --branch warrior git@github.com:zbsarashki/staging-stx.git
cd staging-stx
./setup.sh

Introduction

This layer enables starlingx on poky.

Dependencies

This layer depends on:

	URI: git://git.openembedded.org/meta-openembedded/
	revision: HEAD

	layes: meta-oe
	meta-python
	meta-networking

You are solely responsible for determining the appropriateness of using or redistributing the above dependencies and assume any risks associated with your exercise of permissions under the license.

Maintenance

Maintainer:

Babak A. Sarashki

Building the meta-stx layer

Setup workspace

mkdir -p $P/workspace/{layers,build}
cd $P/workspace/layers

git clone --branch warrior git://git.yoctoproject.org/poky.git
git clone --branch warrior git://git.openembedded.org/meta-openembedded
git clone --branch warrior git://git.yoctoproject.org/meta-virtualization
git clone --branch warrior git://git.yoctoproject.org/meta-cloud-services
git clone --branch warrior git://git.yoctoproject.org/meta-security
git clone --branch warrior git://git.yoctoproject.org/meta-intel
git clone --branch warrior git://git.yoctoproject.org/meta-security
git clone --branch warrior git://git.yoctoproject.org/meta-selinux
git clone --branch warrior https://github.com/intel-iot-devkit/meta-iot-cloud.git
git clone --branch warrior git://git.openembedded.org/meta-python2
git clone --branch warrior https://git.yoctoproject.org/git/meta-dpdk
git clone --branch warrior git@github.com:Wind-River/meta-stx.git
git clone --branch warrior git@github.com:Wind-River/meta-stak-common.git

Add the following layers to conf/bblayers.conf


P=Path to workspace 

cd $P/workspace/layers/poky
source oe-init-build-env $P/workspace/build

cat > conf/bblayers.conf << EOF
# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
POKY_BBLAYERS_CONF_VERSION = "2"
 
BBPATH = "\${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \\
$P/workspace/layers/poky/meta \\
	$P/workspace/layers/poky/meta-poky \\
	$P/workspace/layers/poky/meta-yocto-bsp \\
	$P/workspace/layers/meta-openembedded/meta-oe \\
	$P/workspace/layers/meta-openembedded/meta-networking \\
	$P/workspace/layers/meta-openembedded/meta-filesystems \\
	$P/workspace/layers/meta-openembedded/meta-perl \\
	$P/workspace/layers/meta-openembedded/meta-python \\
	$P/workspace/layers/meta-openembedded/meta-webserver \\
	$P/workspace/layers/meta-openembedded/meta-initramfs \\
	$P/workspace/layers/meta-virtualization \\
	$P/workspace/layers/meta-cloud-services \\
	$P/workspace/layers/meta-cloud-services/meta-openstack \\
	$P/workspace/layers/meta-intel \\
	$P/workspace/layers/meta-security \\
	$P/workspace/layers/meta-security/meta-security-compliance \\
	$P/workspace/layers/meta-selinux \\
	$P/workspace/layers/meta-iot-cloud \\
	$P/workspace/layers/meta-python2 \\
	$P/workspace/layers/meta-dpdk \\
	$P/workspace/layers/meta-stx \\
	$P/workspace/layers/meta-stak-common \\
	"
EOF
	sed -i -e 's/^\(#MACHINE.*\"qemuarm\"\)/MACHINE \?= \"intel-corei7-64\"\n\1/g' conf/local.conf
	echo 'PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"' >> conf/local.conf

Use Case:

Legal Notices

All product names, logos, and brands are property of their respective owners. All company, product and service names used in this software are for identification purposes only. Wind River is a registered trademarks of Wind River Systems, Inc. Linux is a registered trademark of Linus Torvalds.

Disclaimer of Warranty / No Support: Wind River does not provide support and maintenance services for this software, under Wind Rivers standard Software Support and Maintenance Agreement or otherwise. Unless required by applicable law, Wind River provides the software (and each contributor provides its contribution) on an “AS IS” BASIS, WITHOUT WARRANTIES OF ANY KIND, either express or implied, including, without limitation, any warranties of TITLE, NONINFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the software and assume any risks associated with your exercise of permissions under the license.