blob: a2254ea7a500082ca7080f1d0c86306f7088225d (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
|
# 2. Setting up and starting a build
After [setting up the build system](SETUP.md), we can build images or
recipes for a target machine (or BSP).
Running the commands in the instructions below will setup a build for
a selected AMD BSP, and start a build:
### 2.1. Select a BSP
Set the environment variable `MACHINE` to one of the
[supported AMD BSPs](meta-amd-bsp/README.md) (change the
`<machine-name>` in the following example accordingly):
```sh
MACHINE="<machine-name>"
```
### 2.2. Setup the build environment for selected BSP
Source the *oe-init-build-env* script:
```sh
source ./oe-init-build-env build-${MACHINE}-warrior
```
Set the `MACHINE` and `DISTRO` bitbake environment variables in the
`conf/local.conf` (or `auto.conf`):
```sh
tee conf/auto.conf <<EOF
DL_DIR ?= "\${TOPDIR}/../downloads"
SSTATE_DIR ?= "\${TOPDIR}/../sstate-cache"
MACHINE = "${MACHINE}"
DISTRO = "poky-amd"
EOF
```
Add the required layers to the build configuration:
```sh
bitbake-layers add-layer ../meta-openembedded/meta-oe
bitbake-layers add-layer ../meta-openembedded/meta-python
bitbake-layers add-layer ../meta-openembedded/meta-networking
bitbake-layers add-layer ../meta-dpdk
bitbake-layers add-layer ../meta-amd/meta-amd-distro
bitbake-layers add-layer ../meta-amd/meta-amd-bsp
```
### 2.3. Start the build
Build one of the supported image recipes:
```sh
bitbake <image-name> -k
```
###### where `<image-name>` is to be replaced with one of the [supported images](FEATURES.md) for the selected AMD BSP.
###### (e.g. `core-image-sato` or `core-image-base`)
---
#### What's next
Continue to "[section 3 - deploy](DEPLOY.md)" for instructions on
booting the target with the newly built image.
You can also [customize the image](CUSTOMIZE.md) by enabling/disabling
certain configurable features. Make sure to re-build the image before
deploying the customized build.
|
