diff options
Diffstat (limited to 'documentation/sdk-manual/sdk-extensible.xml')
| -rw-r--r-- | documentation/sdk-manual/sdk-extensible.xml | 54 |
1 files changed, 44 insertions, 10 deletions
diff --git a/documentation/sdk-manual/sdk-extensible.xml b/documentation/sdk-manual/sdk-extensible.xml index 4236b165b5..a04164a413 100644 --- a/documentation/sdk-manual/sdk-extensible.xml +++ b/documentation/sdk-manual/sdk-extensible.xml | |||
| @@ -7,22 +7,56 @@ | |||
| 7 | <title>Using the Extensible SDK</title> | 7 | <title>Using the Extensible SDK</title> |
| 8 | 8 | ||
| 9 | <para> | 9 | <para> |
| 10 | This chapter is going to cover all the SDK stuff that is unique | 10 | This chapter describes what you need on your machine in order to use |
| 11 | to the extensible SDK. | 11 | an extensible SDK. |
| 12 | The chapter does not repeat information that also applies to using the | ||
| 13 | standard SDK. | ||
| 14 | The chapter also includes procedures of tasks you can perform using | ||
| 15 | an extensible SDK. | ||
| 16 | <note> | ||
| 17 | The tasks you can perform using a standard SDK are also available | ||
| 18 | using an extensible SDK. | ||
| 19 | For information on using the standard SDK, see the | ||
| 20 | "<link linkend='sdk-using-the-standard-sdk'>Using the Standard SDK</link>" | ||
| 21 | chapter. | ||
| 22 | </note> | ||
| 12 | </para> | 23 | </para> |
| 13 | 24 | ||
| 25 | |||
| 14 | <section id='sdk-setting-up-to-use-the-extensible-sdk'> | 26 | <section id='sdk-setting-up-to-use-the-extensible-sdk'> |
| 15 | <title>Setting Up to Use the Extensible SDK</title> | 27 | <title>Setting Up to Use the Extensible SDK</title> |
| 16 | 28 | ||
| 17 | <para> | 29 | <para> |
| 18 | What do you need to use the extensible SDK that is different from | 30 | Here is a list of items I think need addressed in this section: |
| 19 | the standard SDK? | 31 | <itemizedlist> |
| 20 | What does your system have to have on it? | 32 | <listitem><para><emphasis>Cover differences in the development |
| 21 | What are the recommendations? | 33 | that might be impacted because they are using an extensible |
| 22 | What conditions in your development scenario warrant use of just the | 34 | SDK</emphasis></para> |
| 23 | extensible SDK? | 35 | <para>Presumably, the various development scenarios are |
| 24 | Show any specific procedures needed to get set up to use the | 36 | covered regarding setup in the previous chapter. |
| 25 | extensible SDK. | 37 | Are these impacted because the developer is going to now be |
| 38 | using an extensible SDK? | ||
| 39 | If so, what are the implications? | ||
| 40 | </para></listitem> | ||
| 41 | <listitem><para><emphasis>What new recommendations exist now that | ||
| 42 | the developer is going to be using an extensible SDK?</emphasis></para> | ||
| 43 | <para>We should cover the most common development scenarios | ||
| 44 | that apply when using an extensible SDK. | ||
| 45 | Is there a recommended development flow we want to present | ||
| 46 | when using an extensible SDK? | ||
| 47 | What conditions in a development scenario warrant use of | ||
| 48 | the extensible SDK as compared to the standard SDK? | ||
| 49 | </para></listitem> | ||
| 50 | <listitem><para><emphasis>What procedures do we want to cover to set | ||
| 51 | up the extensible SDK?</emphasis></para> | ||
| 52 | <para>Is it just a matter of building out the SDK using | ||
| 53 | <filename>bitbake -c populate_sdk_ext</filename>? | ||
| 54 | Is there a pre-built extensible SDK laying around they can | ||
| 55 | find and download if they are using a machine that does not | ||
| 56 | have YP installed, which would prevent them from building their | ||
| 57 | own SDK? | ||
| 58 | </para></listitem> | ||
| 59 | </itemizedlist> | ||
| 26 | </para> | 60 | </para> |
| 27 | </section> | 61 | </section> |
| 28 | 62 | ||