Following documentation from
https://git.ostc-eu.org/OSTC/infrastructure/pipelines/-/blob/main/reuse.yaml
Add the reuse job which can fail, since this repository is not compliant
with REUSE yet.

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


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

This file gets removed in the upstream poky recipe for qemuall due to
problems with it in the Yocto autobuilder QA.

On our side we need it in combination with spread so we bring it back
here. Next step would be to investigate why it fails on Yocto QA and get
it fixed upstream.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

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

Add general description of MACHINE and add bblayers to template.

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

Add mosquitto 2.0.7. This recipe is in sync with the one recently added
to upstream meta-networking and should be removed once we rebase to a
newer Yocto that has commit 9428a09002a0a1058b155ff767bd5de5c8929998.

Fixes https://git.ostc-eu.org/OSTC/planning/core-os/-/issues/30



Signed-off-by: Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@huawei.com>

Stefan observed that CI job initializes bitbake with layer configuration
from the layer as checked out by git-repo, and only then switches to the
branch being tested.

This resulted in bitbake incorrectly failing to notice a layer that was
added by the tested patch.

The solution is to move all of the bitbake initialization stage from the
.build jobs "script_before" section, to the "script" section. In effect
any derivative job can use "script_before" to freely alter the source
tree before bitbake is initialized. Due to the lucky arrangement of YAML
anchors, the .build job's "script" keeps running with bitbake
environment sourced, so it can do exactly what one would expect - build
the desired recipe.

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

Bernhard Rosenkränzer authored 4 years ago and Stefan Schmidt committed 4 years ago

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



Signed-off-by: Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@huawei.com>

We have notced that some of ACTS dependencies do not build correctly for
Avenger96. This went unnoticed because the CI system is building the
plain image, that does not include any test dependencies.

Fix that by building the test image instead of the plain image, for
targets based on Linux.

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

ZMK has logic to set CC and CXX to the proper triplet name when the
configure script is invoked with different --build and --host. Normally
this works fine but when the configure script is also invoked with the
environment that picks a specific CC or CXX, such as by passing extra
flags through it, things can misbehave.

Vendor a patch from upstream until the next zmk release.

Fixes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/21


Signed-off-by: Zygmunt Krynicki <me@zygoon.pl>

Zygmunt Krynicki authored 4 years ago and Zygmunt Krynicki committed 4 years ago

This experimental pipeline performs bitbake builds in response to
changes proposed for the layers contained in the meta-ohos repository.

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

All of the staging components are moving to a model where the master
branch follows upstream open harmony gitee repository and the ostc
branch is re-based on that master, and contains additional patches.

The zmk patch was applied at the "local" upstream (ostc branch), so drop
if from the recipe.

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

All of the staging components are moving to a model where the master
branch follows upstream open harmony gitee repository and the ostc
branch is re-based on that master, and contains additional patches.

The zmk patch was applied at the "local" upstream (ostc branch), so drop
if from the recipe.

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

All of the staging components are moving to a model where the master
branch follows upstream open harmony gitee repository and the ostc
branch is re-based on that master, and contains additional patches.

During this switch the history in the master branch was re-set to point
to the mirrored upstream code. OSTC branch was re-based and the
corresponding revision was lost.

The zmk patch was applied at the "local" upstream (ostc branch), so drop
if from the recipe.

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

The OHOS uses unversioned versioned libraries.
Move the naked .so files to the primary package.

This should resolve errors that prevent adding additional tests and test
libraries to the recipe:

    ERROR: ohos-xts-acts-0.0+gitAUTOINC+ca29e6cacc-r0 do_package_qa: QA
    Issue: -dev package contains non-symlink .so: ohos-xts-acts-dev path
    '/work/core2-64-poky-linux/ohos-xts-acts/0.0+gitAUTOINC+ca29e6cacc-r0/packages-split/ohos-xts-acts-dev/usr/lib/libohos-kernel-fs.so'
    -dev package contains non-symlink .so: ohos-xts-acts-dev path
    '/work/core2-64-poky-linux/ohos-xts-acts/0.0+gitAUTOINC+ca29e6cacc-r0/packages-split/ohos-xts-acts-dev/usr/lib/libohos-kernel-utils.so'

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

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

openharmony-image-<variant>-tests images are based on the
openharmony-image-<variant> with addition of the packagegroup-openharmony-tests
package group that aggregates all OpenHarmony tests.

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

packagegroup-openharmony-tests is intended to aggregate OpenHarmony tests
and to be included in the OpenHarmony test images.

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

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

Include file with common definitions to avoid duplication.

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

meta-ohos-foundation is currently unused, therefore it should not
be included in the bblayers.conf.sample file.

meta-ohos-acts layer contains recipes for building OHOS tests.

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>

zephyr is no longer preferred, default DISTRO. Change it
to openharmony-zephyr.

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

meta-ohos-core contains DISTRO configurations that
may be used by Zephyr build. In the future some images
also may be added.

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

Add OpenHarmony wrapper for the Zephyr distro config.
This doesn't add any functionality on top of zephyr.conf
but rather aligns it with openharmony-linux distro naming
convention. DISTRO_VERSION is same as its Linux counterpart.

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

Using the OSTC logo until we have the real OpenHarmony logo in place
later.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@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>

Poky is no longer correct default DISTRO. Change it
to openharmony-linux.

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

Add missing boards to the supported boards list.

Add missing hyphen in `runqemu` command.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@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>

Remove redundant IMAGE_INSTALL_append from local.conf.sample.
openharmony-image-base and openharmony-image-extra images
will include those packages.

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

Add meta-ohos-core to the sample list of layers being
used in the project.
The layer contains:
* Core elements of the OpenHarmony distribution
* Reference images recipes

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

Add recipes for for base and extra (adding i.a. GUI) images.
Both are derived from their core-class counterparts (base and weston).
Each will append necessary package groups.

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

Introduce package group to gather connectivity related
(networking, bluetooth, etc.) applications and tools.

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

Add openharmony-linux base distribution configuration
as a superset of poky.
For now this distro only enables systemd as a default
init manager instead of sysvinit.

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

Add meta-ohos-core layer skeleton.
It is intended to be used to provide OpenHarmony
distributions and images.

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

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

Linux daemon to interact with a network co-processor compatible OT
firmware for Thread network access.

The project itself is in maintenance mode and only accepts fixes and no
new fatures. Consider OpenThread Daemon as replacement.

Closes: https://git.ostc-eu.org/OSTC/planning/core-os/-/issues/3



Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>