Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Dongni He authored 4 years ago and Stefan Schmidt committed 4 years ago

Signed-off-by: Dongni He <dongni.he@huawei.com>

Add general description of MACHINE and add bblayers to template.

Signed-off-by: Ettore Chimenti <ettore.chimenti@seco.com>

Signed-off-by: Robert Drab <robert.drab@huawei.com>

Make a default machine first on the list and in bold (in README.md)
to avoid ambiguity.

Signed-off-by: Robert Drab <robert.drab@huawei.com>

Not only Poky-specific DISTRO_NAME and VERSION will
not be displayed but this string isn't even printed right
before the login prompt.

Signed-off-by: Zbigniew Bodek <zbigniew.bodek@huawei.com>

Explicitly setting `DEPLOY_DIR_IMAGE` is not needed, since we have
`TEMPLATECONF`.
Setting `TEMPLATECONF` on the `source` step makes both `bitbake` and
`runqemu` steps share the same `DISTRO` setting, which sets
`DEPLOY_DIR_IMAGE` properly. Remove it from readme and conf-notes shown
after sourcing the env.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>

Since the default images have changed, switch to
the new ones recommended for OpenHarmony.

Signed-off-by: Zbigniew Bodek <zbigniew.bodek@huawei.com>

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>

We want README pointing to the stable manifest to avoid any issues
with the build process especially for the first time users.

Closes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/8


Signed-off-by: Robert Drab <robert.drab@huawei.com>

Having core-image-minimal as a default first-on-the-list image
can be misleading when adding new boards to the build system
as this image allows only to boot-up minimal system without
any features that the board may support in terms of connectivity, etc.

core-image-full-cmdline, likewise, does not include "kernel-modules"
and can cause similar confusion.

Closes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/7


Signed-off-by: Robert Drab <robert.drab@huawei.com>

Add required meta-layers to bblayers.conf.sample.
Add dependencies to local.conf.sample that provide necessary
packages to enable Ethernet, WiFi and Bluetooth connectivity.
Mention the board in README.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>

Alberto Merciai authored 4 years ago and Ettore Chimenti committed 4 years ago

Co-authored-by: Ettore Chimenti <ettore.chimenti@seco.com>
Co-authored-by: Tommaso Merciai <tommaso.merciai@seco.com>
Co-authored-by: Alberto Merciai <alberto.merciai@seco.com>
Signed-off-by: Ettore Chimenti <ettore.chimenti@seco.com>

meta-ohos and manifest moved from OSTC to OSTC/OHOS subgroup

Signed-off-by: Robert Drab <robert.drab@huawei.com>

OHOS build environment can be quickly set up using
TEMPLATECONF pointing to selected flavour, e.g.
linux, zephyr.

New build directory structure:
all meta layers are stored in the sources directory
alongside poky instead of inside poky

Signed-off-by: Robert Drab <robert.drab@huawei.com>

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

Added Linux to the diagram, so it's clear that OHOS targets
Linux as well as Zephyr etc.

Signed-off-by: Davide Ricci <davide.ricci@huawei.com>
Signed-off-by: Robert Drab <robert.drab@huawei.com>

Leveraging diagrams auto generation from embedded plantuml code

Signed-off-by: Robert Drab <robert.drab@huawei.com>

This file should be a single entry point for meta-ohos documentation,
therefore Getting started section of manifest README was moved here.

Signed-off-by: Robert Drab <robert.drab@huawei.com>

To manage architecture decision records the adr-tools will be used.

Signed-off-by: Robert Drab <robert.drab@huawei.com>

In meta-ohos software architecture is represented using c4model.
Here top-most level diagram of the c4 model.

Signed-off-by: Robert Drab <robert.drab@huawei.com>

README.md initial commit

Signed-off-by: Robert Drab <robert.drab@huawei.com>

Two REDAME.md merged into one; all thirdparty recipes gatherd
inside meta-ohos-foundation subirectory

Signed-off-by: Robert Drab <robert.drab@huawei.com>

Adding recipes for third party ohosinit dependencies:
- cjson library - built directly from github, not from gitee
- libsec - library implementing secure versions of some standard functions

Recipe naming resembles original OHOS repository names
with the exception when the repository contains only
single library source code - in such case recipe name is the
same as the library name it provides

Signed-off-by: Robert Drab <robert.drab@huawei.com>

Two REDAME.md merged into one; all recipes gatherd inside
meta-ohos-foundation subirectory

Signed-off-by: Robert Drab <robert.drab@huawei.com>

Adding recipes for common OHOS headers and libraries:
- syspara-lite-framework - System Parameter library
- syspara-lite-hals-headers - System Parameter HAL header files
- syspara-lite-headers - System Parameter header files
- utils-native-lite - Generic OHOS header files

Recipe naming resembles original OHOS repository names
with the exception when the repository contains only
single library source code - in such case recipe name is the
same as the library name it provides

Signed-off-by: Robert Drab <robert.drab@huawei.com>

Moving all files to subdirectory prior to repository merge.

Signed-off-by: Robert Drab <robert.drab@huawei.com>

Adds minimal set of dependencies required
for the "foundation" application to build
and initialize:
- SAMGR (distributed services manager + headers)
- SAFWK (project containing sources of the foundation app)

Note:  Debugging output is enabled by default on SAFWK
Note2: Currently SAMGR can include OS adapter only for
       Linux (posix) or uC (cmsis). If LiteOS or other
       system is going to be used, please modify
       samgr_git.bb's TARGET_ADAPTER accordingly.

Signed-off-by: Zbigniew Bodek <zbigniew.bodek@huawei.com>

Add empty readme file.