@@ -122,7 +122,7 @@ You must install the software packages required for build. The command is as fol
# export PATH=~/.local/bin:$PATH
```
**NOTE**<br>The hb tool will be installed during the installation of **ohos-build**. If hb tool fails to be installed, [install hb](../../device-dev/quick-start/quickstart-pkg-install-tool.md#hb-installation) again.
>**NOTE**<br>The hb tool will be installed during the installation of **ohos-build**. If hb tool fails to be installed, [install hb](../../device-dev/quick-start/quickstart-pkg-install-tool.md#hb-installation) again.
## Configuration Rules
...
...
@@ -205,7 +205,7 @@ Then, run the build commands in command line (CLI) mode or hb mode.
> Due to the limitation of the image size, the full build for the debug version may fail to be burnt. You are advised to build the binary file for each module separately. Run the following command to build a module separately:
@@ -20,7 +20,7 @@ The chipset solution directory structure is as follows:
└── config.gni # LiteOS_A build configuration
```
**NOTE**<br>The **config.gni** file contains the configuration related to the build of the development board. The parameters in this file are used to compile all OS components and are globally visible during the build process.
**CAUTION**<br>The **config.gni** file contains the configuration related to the build of the development board. The parameters in this file are used to compile all OS components and are globally visible during the build process.
- The **config.gni** file contains the following key parameters:
@@ -47,7 +47,7 @@ The **bundle.json** file of a component is stored in the root directory of the c
}
```
>  **NOTE**<br>Existing components on the LiteOS are configured in the JSON file of the corresponding subsystem in the **build/lite/components** directory. The directory is named in the **{Domain}/{Subsystem}/{Component}** format. The component directory structure is as follows:
> **CAUTION**<br>Existing components on the LiteOS are configured in the JSON file of the corresponding subsystem in the **build/lite/components** directory. The directory is named in the **{Domain}/{Subsystem}/{Component}** format. The component directory structure is as follows:
>  **NOTE**<br>Directories and files must be created for new products based on the preceding rules. The Compilation and Building subsystem scans the configured products based on the rules.
> **NOTE**<br>Directories and files must be created for new products based on the preceding rules. The Compilation and Building subsystem scans the configured products based on the rules.
The key directories and files are described as follows:
...
...
@@ -135,7 +135,7 @@ The key directories and files are described as follows:
-**out** directory of the product, which corresponds to **{root_out_dir}** of GN.
- File system directory **${fs_dir}**, which consists of variables **${root_path}** and **${fs_dir_name}**.
>  **NOTE**<br>**fs.yml** is optional. You do not need to configure it for devices without a file system.
> **NOTE**<br>**fs.yml** is optional. You do not need to configure it for devices without a file system.
6.**vendor/company/product/BUILD.gn**<br>**BUILD.gn** provides the entry for product build. It is used to compile the source code of the solution vendor and copy the startup configuration file. The **BUILD.gn** file in the corresponding product directory will be built by default if a product is selected. The following is an example of the **BUILD.gn** file of a product:
...
...
@@ -184,7 +184,7 @@ You can customize a product solution by assembling any chipset solution and comp
}
```
**NOTE**<br>Before the build, the Compilation and Building subsystem checks the validity of the fields in **config.json**. The **device_company**, **board**, **kernel_type**, and **kernel_version** fields must match the chipset solution, and the **subsystem** and **component** fields must match the component description in **build/lite/components**.
>**NOTE**<br>Before the build, the Compilation and Building subsystem checks the validity of the fields in **config.json**. The **device_company**, **board**, **kernel_type**, and **kernel_version** fields must match the chipset solution, and the **subsystem** and **component** fields must match the component description in **build/lite/components**.
3. Implement OS adaptation APIs. Create the **hals** directory in the product directory and save the source code as well as the build script for OS adaptation in the **hals** directory.
@@ -60,7 +60,7 @@ The dependency between modules can be classified into **deps** (left in the figu
}
```
**NOTE**<br>The dependency between components must be written in the format of **Component name:Module name** in **external_deps**. The dependent module must be declared in **inner_kits**.
> **NOTE**<br>The dependency between components must be written in the format of **Component name:Module name** in **external_deps**. The dependent module must be declared in **inner_kits**.
