| Message ID | 20240618143536.453241-1-ross.burton@arm.com |
|---|---|
| State | New |
| Headers | show |
| Series | documentation/runfvp: use IMAGE_CLASSES instead of INHERIT | expand |
On Tue, 18 Jun 2024 14:35:36 +0000, Ross Burton wrote: > The fvpboot class specifically hooks into the image creation, so it > should use IMAGE_CLASSES instead of INHERIT (which is global in scope). > > Applied, thanks! [1/1] documentation/runfvp: use IMAGE_CLASSES instead of INHERIT commit: 156141c014195c1d48e663ae6867eb307190d4d6 Best regards,
diff --git a/documentation/runfvp.md b/documentation/runfvp.md index ed14d44a..be2d8614 100644 --- a/documentation/runfvp.md +++ b/documentation/runfvp.md @@ -4,10 +4,10 @@ The `runfvp` tool in meta-arm makes it easy to run Yocto Project disk images ins ## Running images with `runfvp` -To build images with the FVP integration, the `fvpboot` class needs to be inherited. If the machine does not do this explicitly it can be done in `local.conf`: +To build images with the FVP integration, the `fvpboot` image class needs to be inherited. If the machine does not do this explicitly it can be done in `local.conf`: ``` -INHERIT += "fvpboot" +IMAGE_CLASSES += "fvpboot" ``` The class will download the correct FVP and write a `.fvpconf` configuration file when an image is built.
The fvpboot class specifically hooks into the image creation, so it should use IMAGE_CLASSES instead of INHERIT (which is global in scope). Signed-off-by: Ross Burton <ross.burton@arm.com> --- documentation/runfvp.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)