Skip to content
Snippets Groups Projects
Commit 592529bd authored by NawabAhmad's avatar NawabAhmad
Browse files

Add meta-openharmony content to the existing RTD docs


Signed-off-by: default avatarNawabAhmad <nawab.ahmad.reshi@huawei.com>
parent 49726aa0
No related branches found
No related tags found
1 merge request!30flavours/zephyr/local.conf.sample: Bump CONF_VERSION
......@@ -7,6 +7,20 @@
|main_project_name| Build Architecture
######################################
Oniro build architecture is composed of multifaceted, independent, modular, and
reusable building blocks. In order to build OpenHarmony based images and its
components, meta-openharmony component serves as one of the major building blocks.
In context of OpenHarmony, the OS essentially builds upon various components and
respective functionalities, and in terms of functionality, the meta-openharmony
component principally helps to desolate the barrier of hardware boundaries, thus
inevitably transcending the classical OS dichotomy.
Architecturally, the `meta-openharmony` is a bitbake layer that contains recipes
for building OpenHarmony images and components. The meta-openharmony includes a
number of different repo manifest files, which you can use to fetch all repositories
needed for building OpenHarmony. To have a successful build image, ensure that the
undelying dependencies and the build procedure is followed in chronological order.
``Oniro Project`` architecture is documented using `c4 model <https://c4model.com/>`_.
.. contents::
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment