From: Scott Rifenbark Date: Thu, 12 Jul 2018 18:35:05 +0000 (-0700) Subject: sdk-manual: Updates to "Adjusting the Extensible SDK to Suit Build Host" X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=16eddf2be6a35ddee0b2b3e193bd8c84fcc20e31;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git sdk-manual: Updates to "Adjusting the Extensible SDK to Suit Build Host" I updated this section with clearer text. (From yocto-docs rev: 433388ff37297d905c465a5f05d93953dfe062c5) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- diff --git a/documentation/sdk-manual/sdk-appendix-customizing.xml b/documentation/sdk-manual/sdk-appendix-customizing.xml index b1bd03f037c..2d1788660b8 100644 --- a/documentation/sdk-manual/sdk-appendix-customizing.xml +++ b/documentation/sdk-manual/sdk-appendix-customizing.xml @@ -78,11 +78,13 @@ -
- Adjusting the Extensible SDK to Suit Your Build System Setup +
+ Adjusting the Extensible SDK to Suit Your Build Host's Setup - In most cases, the extensible SDK defaults should work. + In most cases, the extensible SDK defaults should work with your + build host's + setup. However, some cases exist for which you might consider making adjustments: @@ -93,33 +95,43 @@ variable and you do not need or want those classes enabled in the SDK, you can blacklist them by adding them to the SDK_INHERIT_BLACKLIST - variable. - The default value of SDK_INHERIT_BLACKLIST - is set using the "?=" operator. - Consequently, you will need to either set the complete value - using "=" or append the value using "_append". + variable as described in the fourth bullet of the previous + section. + + The default value of + SDK_INHERIT_BLACKLIST is set using + the "?=" operator. + Consequently, you will need to either define the entire + list by using the "=" operator, or you will need to append + a value using either "_append" or the "+=" operator. + You can learn more about these operators in the + "Basic Syntax" + section of the BitBake User Manual. + . If you have classes or recipes that add additional tasks to - the standard build flow (i.e. that execute as part of building - the recipe as opposed to needing to be called explicitly), then - you need to do one of the following: + the standard build flow (i.e. the tasks execute as the recipe + builds as opposed to being called explicitly), then you need + to do one of the following: - Ensure the tasks are shared state tasks (i.e. their - output is saved to and can be restored from the shared - state cache), or that the tasks are able to be - produced quickly from a task that is a shared state - task and add the task name to the value of + After ensuring the tasks are + shared state + tasks (i.e. the output of the task is saved to and + can be restored from the shared state cache) or + ensuring the tasks are able to be produced quickly from + a task that is a shared state task, add the task name + to the value of SDK_RECRDEP_TASKS. Disable the tasks if they are added by a class and you do not need the functionality the class provides in the extensible SDK. - To disable the tasks, add the class to - SDK_INHERIT_BLACKLIST as previously - described. + To disable the tasks, add the class to the + SDK_INHERIT_BLACKLIST variable + as described in the previous section.