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.
Oniro Project build infrastructure is designed to run atop variety of OS kernels ranging from RTOSes to Linux.
oniro is an umbrella of meta layers containing build’s meta-data
required for compiling Oniro Project images. The architecture supports plugging
One of the core aims of Oniro Project is to provide a stable foundation for product development. In doing so, the project tries its best to align all the included components to their respective LTS (long-term support) versions. The build system is one of the core components used in Oniro and its version adheres to the same principle.
The current version of the projects uses
kirkstone version of Yocto
project, the build system of choice in Oniro Project. This ensures that
all the Yocto layers brought in are either on their respective
kirkstone branch/version or, in the absence of that, on a