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

The manifest repository now offers new hidden jobs, that make
customization and reuse easier. Those allow us to remove bulk of the
custom logic, again, reducing everything to mere configuration.

The build-docs and update-docs jobs are entirely replaced by .build-docs
and .aggregate-docs (name change without logic change).

Custom .build job is split into smaller changes to the .workspace and
.bitbake-workspace jobs. Lastly, the variable OHOS_CI_GIT_REPO_PATH
is no longer relative to sources/ but includes it explicitly.

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

* 'pyOCD-flashtool -l' command syntax rectified as 'pyocd-flashtool -l',
 fixes issue#39

Signed-off-by: Arul Kumaran <arulkumaran.devarajan@huawei.com>

Due to a configuration bug in upstream, the build system outputs a
configuration warning similar to:

---------- CONFIG_SERIAL_OF_PLATFORM -----------------
Config: CONFIG_SERIAL_OF_PLATFORM
From:
[...]/kernel-source/.kernel-meta/configs/v5.10/standard/cfg/8250.cfg
Requested value:  CONFIG_SERIAL_OF_PLATFORM=y
Actual value:

Avoid this by disabling the specific config.

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

When building with Python 3.9+ on the host, there are various ways the
build will fail. Fixes to address these issues are already in newer
version of the component so this only backports two related patches.

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

To address the "demo" to "blueprint" rename, zephyr-demo-smarthome-base
repository was also renamed accordingly. Reflect this change in the
build recipe.

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

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

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

"openharmony-linux-demo-dashboard" was deprecated in favour of
"openharmony-linux-blueprint-dashboard".

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

The mechanism and value format of OHOS_DEPRECATED_DISTROS is identical
to OHOS_DEPRECATED_COLLECTIONS.

Deprecated distro configurations can be either completely removed or
replaced by another configuration. The format of OHOS_DEPRECATED_DISTROS
is a list of <DEPRECATED_DISTRO>:<REPLACEMENT_DISTRO>. When
<REPLACEMENT_DISTRO> is not provided, the distro was removed without a
replacement.

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

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

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

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

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

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

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

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

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

As the ohos-sanity bbclass is not kernel-specific, the inclusion is done
through an include file.

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

This bbclass is meant to handle various build configuration checks. As
per the current implementation, it handles collections deprecation.

Deprecated collections can be either completely removed or replaced by
another layer. The format of OHOS_DEPRECATED_COLLECTIONS is a list of
<DEPRECATED_COLLECTION>:<REPLACEMENT_COLLECTION>. When
<REPLACEMENT_COLLECTION> is not provided, the layer was removed without
a replacement.

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

With the 0.1.0 release done we are now back in development mode.
Indicate this by setting the version to 0.1.99. If we ned to provide
stable update releases to 0.1.0 they will come from a release branch as
0.1.1 .. 0.1.n.

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

Show Dashboard/SmartHome demo setup on a puml diagram.

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

- Add building and flashing guidelines for SmartHome demo
  endpoints

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

Demo consists of two IOT endpoints: sensors board
and bulb/LED board.
Add image to specialize base settings to the LED board's
configuration. In this case settings related to LCD display
and sensors are disabled.

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

Demo consists of two IOT endpoints: sensors board
and bulb/LED board.
Add image to specialize base settings to the sensors board's
configuration. In this case LED control is disabled.

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

Add meta-zephyr from our local fork to the required layers.
This should be changed to upstream version when it's
aligned with our local state.

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

- Allows for building SmartHome Demo Zephyr application
- Requires meta-zephyr layer
- Application is going to be built with all options enabled (default)

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

- Remove demo description and HOWTO from meta-ohos-demo README.md
- Improve building guidelines in the smart-panel.rst
  Reference to building an image for Avenger96 + explicit command
  for building dashboard demo.

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

This commit marks the final Aladeen 0.1.0 release.

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

Add instructions for installing repo on various distributions through
our COPR and OBS repositories

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

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

For qemuarm  builds we have seen the case that ths gcc plugins build
inside the linux kernel has been failing on missing header files gmp.h,
mcp.h and others. The native dependencies have been available, but the
kernel Makefile did not have the correct include path for the headers.

Neither poky dunfell nor master has this problem. No upstreaming needed.

Closes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/merge_requests/93



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

Sebastian Serewa authored 3 years ago and Stefan Schmidt committed 3 years ago

To reference those section labels of the documentation, so they can be referenced
from the other parts of the documentation.

Signed-off-by: Sebastian Serewa <sebastian.serewa@huawei.com>

There are two separate issues here:

- CI_BRANCH_NAME doesn't exist, we want CI_COMMIT_BRANCH instead.
- The rules engine doesn't handle quotes in the normal sense.
Quotes are only allowed on literals, not variable references.

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

CI_BRANCH_NAME doesn't exist

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

The rules engine doesn't handle quotes in the normal sense.
Quotes are only allowed on literals, not variable references.

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

Set rule to run our build pipeline for git tags as well.

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

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

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

When documentation changes, trigger the docs pipeline to update the
aggregated documentation view.

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