diff options
Diffstat (limited to 'documentation/sdk-manual/sdk-using.xml')
| -rw-r--r-- | documentation/sdk-manual/sdk-using.xml | 54 |
1 files changed, 46 insertions, 8 deletions
diff --git a/documentation/sdk-manual/sdk-using.xml b/documentation/sdk-manual/sdk-using.xml index eb024f917c..e3dc6e22a1 100644 --- a/documentation/sdk-manual/sdk-using.xml +++ b/documentation/sdk-manual/sdk-using.xml | |||
| @@ -7,20 +7,58 @@ | |||
| 7 | <title>Using the Standard SDK</title> | 7 | <title>Using the Standard SDK</title> |
| 8 | 8 | ||
| 9 | <para> | 9 | <para> |
| 10 | This chapter is going to cover all the SDK stuff that is common | 10 | This chapter describes how to use a standard SDK. |
| 11 | to both the SDK and the extensible SDK. | 11 | Information covers installing the SDK and task-based procedures common |
| 12 | for developing with a standard SDK. | ||
| 13 | <note> | ||
| 14 | The tasks you can perform using a standard SDK are also applicable | ||
| 15 | when you are using an extensible SDK. | ||
| 16 | For information on the differences when using an extensible SDK as | ||
| 17 | compared to an extensible SDK, see the | ||
| 18 | "<link linkend='sdk-extensible'>Using the Extensible SDK</link>" | ||
| 19 | chapter. | ||
| 20 | </note> | ||
| 12 | </para> | 21 | </para> |
| 13 | 22 | ||
| 14 | <section id='sdk-setting-up-to-use-the-standard-sdk'> | 23 | <section id='sdk-setting-up-to-use-the-standard-sdk'> |
| 15 | <title>Setting Up to Use the Standard SDK</title> | 24 | <title>Setting Up to Use the Standard SDK</title> |
| 16 | 25 | ||
| 17 | <para> | 26 | <para> |
| 18 | What do you need to use the SDK? | 27 | Here is a list of items I think need addressed in this section: |
| 19 | What does your system have to have on it? | 28 | <itemizedlist> |
| 20 | What are the recommendations? | 29 | <listitem><para><emphasis>What is your situation?</emphasis></para> |
| 21 | What conditions in your development scenario warrant use of just the | 30 | <para>In other words, is the developer on a machine that |
| 22 | standard SDK as compared to the extensible SDK? | 31 | has YP on it? |
| 23 | Show any specific procedures needed to get set up to use the SDK. | 32 | Are they on a machine that does not? |
| 33 | Is the image they are developing against available as a | ||
| 34 | pre-built, down-loadable image and can they get it?</para> | ||
| 35 | <para>Depending on the scenario, there are different ways | ||
| 36 | to make sure the machine they are using is ready to use a | ||
| 37 | standard SDK. | ||
| 38 | I think we need to cover the various situations in this | ||
| 39 | section. | ||
| 40 | </para></listitem> | ||
| 41 | <listitem><para><emphasis>What are the recommendations?</emphasis></para> | ||
| 42 | <para>What is the most common development scenario? | ||
| 43 | Is there a recommended development flow we want to present | ||
| 44 | when using a standard SDK? | ||
| 45 | What conditions in a development scenario warrant use of | ||
| 46 | just the standard SDK as compared to the extensible SDK? | ||
| 47 | </para></listitem> | ||
| 48 | <listitem><para><emphasis>What procedures do we want to cover to set up | ||
| 49 | the standard SDK?</emphasis></para> | ||
| 50 | <para>There is a ton of setup information in the | ||
| 51 | current ADT manual regarding getting, building, and installing | ||
| 52 | an SDK. | ||
| 53 | We would ignore the stuff about the ADT installer script | ||
| 54 | since I presume that is going away. | ||
| 55 | But, there are steps to download and existing | ||
| 56 | <filename>.sh</filename> install script, build out the | ||
| 57 | toolchains assuming your system has YP on it and you can run | ||
| 58 | BitBake, getting the root filesystem, getting an image so you | ||
| 59 | run QEMU on your system, etc. | ||
| 60 | </para></listitem> | ||
| 61 | </itemizedlist> | ||
| 24 | </para> | 62 | </para> |
| 25 | </section> | 63 | </section> |
| 26 | 64 | ||