diff --git a/README.md b/README.md
index 0662b6e0d5ca0c85c8877ecfff80fd9d55720929..3a19f32280762b765a768ddab589f2a2ff7c4469 100644
--- a/README.md
+++ b/README.md
@@ -23,53 +23,98 @@ Once git repo has been installed we can use it to clone the necessary repositori
$ mkdir ohos; cd ohos
$ repo init -u https://git.ostc-eu.org/OSTC/manifest.git
$ repo sync
- $ cd poky
- poky$ . oe-init-build-env
-Working directory will automatically change to ./poky/build. Add layers for
-other kernels. Layers for poky were added automatically by sourcing
-`oe-init-build-env`.
+Above commands should result in the following directory structure:
- build$ bitbake-layers add-layer ../meta-openembedded/meta-oe
- build$ bitbake-layers add-layer ../meta-openembedded/meta-python
- build$ bitbake-layers add-layer ../meta-zephyr
- build$ bitbake-layers add-layer ../meta-freertos
+ ./ohos/
+ └── sources
+ ├── meta-freertos
+ ├── meta-ohos
+ ├── meta-openembedded
+ ├── meta-zephyr
+ ├── <various yocto layers>
+ └── poky
-Build distro of your choice:
+### OHOS flavours
-For Poky-tiny you can choose any of the following machines:
-qemux86, qemux86-64, qemuarm, qemuarmv5
+OpenHarmony can be hosted on top of variety of kernels.
+Currently supported kernels (a.k.a. OHOS flavours) are Linux, Zephyr
+and FreeRTOS (experimental).
- build$ DISTRO=poky-tiny MACHINE=qemux86 bitbake core-image-minimal
+To build OHOS flavour issue following commands:
+ $ TEMPLATECONF=../sources/meta-ohos/flavours/<lower_case_flavour> . ./sources/poky/oe-init-build-env build-<flavour>-<target_machine>
+ $ bitbake <image-name>
-For Zephyr you can choose any of the following machines:
-acrn, arduino-101-ble, arduino-101, arduino-101-sss, qemu-cortex-m3, qemu-nios2, qemu-x86
+MACHINE variable can be set up in conf/local.conf file under build directory
+or via command line, e.g.:
- build$ DISTRO=zephyr MACHINE=qemu-x86 bitbake zephyr-philosophers
+ $ MACHINE=<target_machine> bitbake <image-name>
-For FreeRTOS you can choose any of the following machines: qemuarmv5.
+#### OHOS Linux flavour
- build$ DISTRO=freertos MACHINE=qemuarmv5 bitbake freertos-demo
+OHOS Linux flavour is based on _poky_ distribution.
-For Zephyr, `zephyr-philosophers` is the one of sample applications available
-in meta-zephyr layer by Yocto project. It's easy to build other samples using
-recipes available in `meta-zephyr/recipes-kernel/zephyr-kernel/` directory.
+Supported images:
+- core-image-minimal
+- core-image-full-cmdline
-## Running OpenHarmony image
+Supported machines:
+- qemux86-64 (default)
+- qemux86
+- qemuarm
+- qemuarm64
-When the build is finished, you can run the image by issuing:
+Example:
- # For poky
- build$ runqemu qemux86 ramfs qemuparams="-nographic"
- # For Zephyr
- build$ DEPLOY_DIR_IMAGE=tmp-newlib/deploy/images/qemu-x86 runqemu qemu-x86
- # For FreeRTOS
- build$ runqemu qemuarmv5
+ $ TEMPLATECONF=../sources/meta-ohos/flavours/linux . ./sources/poky/oe-init-build-env build-ohos-linux-qemux86-64
+ $ bitbake core-image-minimal
+
+You can test the image built for the qemux86-64 target by issuing:
+
+ $ runqemu qemux86-64 qemuparams="-nographic"
+
+After successful bootup, you should see following:
+
+ Poky (Yocto Project Reference Distro) 3.1.4 qemux86-64 /dev/ttyS0
+
+ qemux86-64 login:
+
+Default login is _root_ without a password.
+After login you should see prompt:
+
+ root@qemux86-64:~#
+
+To exit qemu, you can either shut down the system:
+
+ root@qemux86:~# poweroff -f
+
+or close qemu using key combination:
+
+ Ctrl-a followed by 'x'
+
+#### OHOS Zephyr flavour
+
+OHOS Zephyr flavour is based on _zephyr_ distribution and supports following images / machines:
+
+Supported images:
+- zephyr-philosophers
+
+Supported machines:
+- qemu-cortex-m3
+- qemu-x86 (default)
+
+Example:
+
+ $ TEMPLATECONF=../sources/meta-ohos/flavours/zephyr . ./sources/poky/oe-init-build-env build-ohos-zephyr-qemu-x86
+ $ bitbake zephyr-philosophers
+
+You can test the image built for the qemu-x86 target by issuing:
+
+ $ DEPLOY_DIR_IMAGE=tmp-newlib/deploy/images/qemu-x86 runqemu qemu-x86
After successful bootup, you should see following:
- # For Zephyr
Booting from ROM..*** Booting Zephyr OS build zephyr-v2.4.0 ***
Philosopher 0 [P: 3] THINKING [ 300 ms ]
Philosopher 1 [P: 2] EATING [ 575 ms ]
@@ -77,13 +122,31 @@ After successful bootup, you should see following:
Philosopher 3 [P: 0] EATING [ 525 ms ]
Philosopher 4 [C: -1] THINKING [ 475 ms ]
- # For poky
- qemux86 login:
- # Default login is _root_ without a password.
- # After login you should see prompt:
- root@qemux86:~#
+To exit qemu, use key combination:
+
+ Ctrl-a followed by 'x'
+
+#### OHOS FreeRTOS flavour
+
+OHOS FreeRTOS flavour is based on _freertos_ distribution and supports following images / machines:
+
+Supported images:
+- freertos-demo
+
+Supported machines:
+- qemuarmv5
+
+Example:
+
+ $ TEMPLATECONF=../sources/meta-ohos/flavours/freertos . ./sources/poky/oe-init-build-env build-ohos-freertos-qemuarmv5
+ $ bitbake freertos-demo
+
+You can test the image built for the qemuarmv5 target by issuing:
+
+ $ runqemu qemuarmv5
+
+After successful bootup, you should see following:
- # For FreeRTOS
###### - FreeRTOS sample application - ######
A text may be entered using a keyboard.
@@ -98,15 +161,10 @@ After successful bootup, you should see following:
Notification Received
Waiting For Notification - Blocked...
-To exit qemu, you can either shut down the system:
-
- root@qemux86:~# poweroff -f
-
-or close qemu using key combination:
+To exit qemu, use key combination:
Ctrl-a followed by 'x'
-
# meta-ohos architecture
All decisions for architecturally significant requirements are documented using
diff --git a/flavours/freertos/bblayers.conf.sample b/flavours/freertos/bblayers.conf.sample
new file mode 100644
index 0000000000000000000000000000000000000000..6688bf723c10eb829bb7a8a415d312f03fd866ee
--- /dev/null
+++ b/flavours/freertos/bblayers.conf.sample
@@ -0,0 +1,14 @@
+# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
+# changes incompatibly
+POKY_BBLAYERS_CONF_VERSION = "2"
+
+BBPATH = "${TOPDIR}"
+BBFILES ?= ""
+
+BBLAYERS ?= " \
+ ##OEROOT##/meta \
+ ##OEROOT##/meta-poky \
+ ##OEROOT##/meta-yocto-bsp \
+ ##OEROOT##/../meta-freertos \
+ ##OEROOT##/../meta-ohos/meta-ohos-foundation \
+ "
diff --git a/flavours/freertos/conf-notes.txt b/flavours/freertos/conf-notes.txt
new file mode 100644
index 0000000000000000000000000000000000000000..de9d172e936e4b968405d5875a5ee6cf831ebf06
--- /dev/null
+++ b/flavours/freertos/conf-notes.txt
@@ -0,0 +1,13 @@
+
+### Shell environment set up for builds. ###
+
+#####################################
+# FreeRTOS support is experimental! #
+#####################################
+
+You can now run 'bitbake freertos-demo'
+
+You can also run generated qemu images with a command:
+
+ $ runqemu qemuarmv5
+
diff --git a/flavours/freertos/local.conf.sample b/flavours/freertos/local.conf.sample
new file mode 100644
index 0000000000000000000000000000000000000000..7a5d0cb538e962c25254d847114248d356b944b2
--- /dev/null
+++ b/flavours/freertos/local.conf.sample
@@ -0,0 +1,71 @@
+#
+# 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
+# #
+# This sets the default machine to be qemuarmv5 if no other machine is selected:
+MACHINE ??= "qemuarmv5"
+
+#
+# Default policy config
+#
+DISTRO = "freertos"
+
+#
+# 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 rpm:
+PACKAGE_CLASSES ?= "package_rpm"
+
+#
+# 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.
+#
+# Building FreeRTOS using meta-freertos is currently failing without debug-tweaks!
+#
+EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
+
+# 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 = "1"
diff --git a/flavours/linux/bblayers.conf.sample b/flavours/linux/bblayers.conf.sample
new file mode 100644
index 0000000000000000000000000000000000000000..512f910912043e5bde2f06eea35a06d2f58aa87a
--- /dev/null
+++ b/flavours/linux/bblayers.conf.sample
@@ -0,0 +1,13 @@
+# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
+# changes incompatibly
+POKY_BBLAYERS_CONF_VERSION = "2"
+
+BBPATH = "${TOPDIR}"
+BBFILES ?= ""
+
+BBLAYERS ?= " \
+ ##OEROOT##/meta \
+ ##OEROOT##/meta-poky \
+ ##OEROOT##/meta-yocto-bsp \
+ ##OEROOT##/../meta-ohos/meta-ohos-foundation \
+ "
diff --git a/flavours/linux/conf-notes.txt b/flavours/linux/conf-notes.txt
new file mode 100644
index 0000000000000000000000000000000000000000..d4c19e0b18aca45854ebc17d3bab9873a19dd5b1
--- /dev/null
+++ b/flavours/linux/conf-notes.txt
@@ -0,0 +1,24 @@
+
+### Shell environment set up for builds. ###
+
+You can now run 'bitbake <target>'
+
+Supported targets:
+- core-image-minimal
+- core-image-full-cmdline
+
+Supported machines:
+- qemux86-64 (default)
+- qemux86
+- qemuarm
+- qemuarm64
+
+MACHINE variable can be set up in conf/local.conf file under build directory
+or via command line, e.g.:
+
+ $ MACHINE=<supported_machine> bitbake <target>
+
+You can also run generated qemu images with a command:
+
+ $ runqemu qemux86-64 qemuparams="-nographic"
+
diff --git a/flavours/linux/local.conf.sample b/flavours/linux/local.conf.sample
new file mode 100644
index 0000000000000000000000000000000000000000..f71864a597edfd3aa75c2e47087573d75fe4c155
--- /dev/null
+++ b/flavours/linux/local.conf.sample
@@ -0,0 +1,258 @@
+#
+# 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-64"
+
+#
+# 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 ?= "poky"
+# As an example of a subclass there is a "bleeding" edge policy configuration
+# where many versions are set to the absolute latest code from the upstream
+# source control systems. This is just mentioned here as an example, its not
+# useful to most new users.
+# DISTRO ?= "poky-bleeding"
+
+#
+# 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 rpm:
+PACKAGE_CLASSES ?= "package_rpm"
+
+#
+# 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 and x86_64
+#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
+# - 'image-mklibs' to reduce shared library files size for an image
+# - 'image-prelink' in order to prelink the filesystem image
+# 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
+USER_CLASSES ?= "buildstats image-mklibs image-prelink"
+
+#
+# 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 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.
+BB_DISKMON_DIRS ??= "\
+ STOPTASKS,${TMPDIR},1G,100K \
+ STOPTASKS,${DL_DIR},1G,100K \
+ STOPTASKS,${SSTATE_DIR},1G,100K \
+ STOPTASKS,/tmp,100M,100K \
+ ABORT,${TMPDIR},100M,1K \
+ ABORT,${DL_DIR},100M,1K \
+ ABORT,${SSTATE_DIR},100M,1K \
+ ABORT,/tmp,10M,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.
+#SSTATE_MIRRORS ?= "\
+#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
+#file://.* file:///some/local/dir/sstate/PATH"
+
+#
+# Yocto Project SState Mirror
+#
+# The Yocto Project has prebuilt artefacts available for its releases, you can enable
+# use of these by uncommenting the following line. This will mean the build uses
+# the network to check for artefacts at the start of builds, which does slow it down
+# equally, it will also speed up the builds by not having to build things if they are
+# present in the cache. It assumes you can download something faster than you can build it
+# which will depend on your network.
+#
+#SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH"
+
+#
+# Qemu configuration
+#
+# By default native qemu will build with a builtin VNC server where graphical output can be
+# seen. The line below enables the SDL UI frontend too.
+PACKAGECONFIG_append_pn-qemu-system-native = " sdl"
+# 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.
+#ASSUME_PROVIDED += "libsdl2-native"
+
+# You can also enable the Gtk UI frontend, which takes somewhat longer to build, but adds
+# a handy set of menus for controlling the emulator.
+#PACKAGECONFIG_append_pn-qemu-system-native = " gtk+"
+
+#
+# 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 "<HOSTNAME>:<PORT>" format
+#
+#BB_HASHSERVE = "auto"
+#BB_SIGNATURE_HANDLER = "OEEquivHash"
+
+# 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 = "1"
diff --git a/flavours/zephyr/bblayers.conf.sample b/flavours/zephyr/bblayers.conf.sample
new file mode 100644
index 0000000000000000000000000000000000000000..46182288378da4e734b87dc0d82a4c9cf64a2629
--- /dev/null
+++ b/flavours/zephyr/bblayers.conf.sample
@@ -0,0 +1,14 @@
+# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
+# changes incompatibly
+POKY_BBLAYERS_CONF_VERSION = "2"
+
+BBPATH = "${TOPDIR}"
+BBFILES ?= ""
+
+BBLAYERS ?= " \
+ ##OEROOT##/meta \
+ ##OEROOT##/../meta-openembedded/meta-oe \
+ ##OEROOT##/../meta-openembedded/meta-python \
+ ##OEROOT##/../meta-zephyr \
+ ##OEROOT##/../meta-ohos/meta-ohos-foundation \
+ "
diff --git a/flavours/zephyr/conf-notes.txt b/flavours/zephyr/conf-notes.txt
new file mode 100644
index 0000000000000000000000000000000000000000..96210cdb82eb5854f57f11f0ae26d164c97f5bad
--- /dev/null
+++ b/flavours/zephyr/conf-notes.txt
@@ -0,0 +1,18 @@
+
+### Shell environment set up for builds. ###
+
+You can now run 'bitbake zephyr-philosophers'
+
+Supported machines:
+- qemu-cortex-m3
+- qemu-x86 (default)
+
+MACHINE variable can be set up in conf/local.conf file under build directory
+or via command line, e.g.:
+
+ $ MACHINE=<supported_machine> bitbake <target>
+
+You can also run generated qemu images with a command:
+
+ $ DEPLOY_DIR_IMAGE=tmp-newlib/deploy/images/qemu-x86 runqemu qemux86
+
diff --git a/flavours/zephyr/local.conf.sample b/flavours/zephyr/local.conf.sample
new file mode 100644
index 0000000000000000000000000000000000000000..b05f4d778b28c133683575573cfdb3e67ccb7980
--- /dev/null
+++ b/flavours/zephyr/local.conf.sample
@@ -0,0 +1,48 @@
+#
+# 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 ?= "qemu-cortex-m3"
+#MACHINE ?= "qemu-x86"
+#
+# This sets the default machine to be qemu-x86 if no other machine is selected:
+MACHINE ??= "qemu-x86"
+
+#
+# Default policy config
+#
+DISTRO = "zephyr"
+
+#
+# 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 rpm:
+PACKAGE_CLASSES ?= "package_rpm"
+
+# 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 = "1"