From 2708ce28014e7f61d8dd09362ad6291dc474c5c1 Mon Sep 17 00:00:00 2001 From: Alexander Kanavin Date: Mon, 18 Mar 2024 16:02:10 +0100 Subject: sdk-manual: correctly describe separate build-sysroots tasks in direct sdk workflows They were separated in https://git.yoctoproject.org/poky/commit/?id=63e53fb8b60d38315015844bd3357fa1649cd639 (From yocto-docs rev: 7cb8ee0b922c57a2fc7100eca585463e888964be) Signed-off-by: Alexander Kanavin Reviewed-by: Michael Opdenacker Signed-off-by: Steve Sakoman --- documentation/sdk-manual/extensible.rst | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/documentation/sdk-manual/extensible.rst b/documentation/sdk-manual/extensible.rst index 355c6cb0e4..d335e78623 100644 --- a/documentation/sdk-manual/extensible.rst +++ b/documentation/sdk-manual/extensible.rst @@ -74,7 +74,7 @@ Setting up the Extensible SDK environment directly in a Yocto build $ bitbake meta-ide-support $ bitbake -c populate_sysroot gtk+3 # or any other target or native item that the application developer would need - $ bitbake build-sysroots + $ bitbake build-sysroots -c build_native_sysroot && bitbake build-sysroots -c build_target_sysroot Setting up the Extensible SDK from a standalone installer --------------------------------------------------------- @@ -1226,8 +1226,12 @@ In this scenario, the Yocto build tooling, e.g. ``bitbake`` is directly accessible to build additional items, and it can simply be executed directly:: + $ bitbake curl-native + # Add newly built native items to native sysroot + $ bitbake build-sysroots -c build_native_sysroot $ bitbake mesa - $ bitbake build-sysroots + # Add newly built target items to target sysroot + $ bitbake build-sysroots -c build_target_sysroot When using a standalone installer for the Extensible SDK -------------------------------------------------------- -- cgit v1.2.3-54-g00ecf