diff options
Diffstat (limited to 'documentation/sdk-manual/sdk-intro.xml')
-rw-r--r-- | documentation/sdk-manual/sdk-intro.xml | 39 |
1 files changed, 34 insertions, 5 deletions
diff --git a/documentation/sdk-manual/sdk-intro.xml b/documentation/sdk-manual/sdk-intro.xml index 99f807e056..5b12fcff64 100644 --- a/documentation/sdk-manual/sdk-intro.xml +++ b/documentation/sdk-manual/sdk-intro.xml | |||
@@ -27,7 +27,19 @@ | |||
27 | </para> | 27 | </para> |
28 | 28 | ||
29 | <para> | 29 | <para> |
30 | Describe what a standard SDK is as compared to the extensible SDK. | 30 | A standard SDK consists of a cross-development toolchain that contains |
31 | a compiler, debugger, and various miscellaneous tools; libraries, | ||
32 | headers, and symbols to match an image; and environment setup script. | ||
33 | You can use this SDK to independently develop and test code that is | ||
34 | destined to run on some target machine. | ||
35 | </para> | ||
36 | |||
37 | <para> | ||
38 | An extensible SDK consists of everything that the standard SDK has plus | ||
39 | tools that allow you to easily add new applications and libraries to | ||
40 | an image, modify the source of an existing component, test changes on | ||
41 | the target hardware, and easily integrate an application into the | ||
42 | the Yocto Project build system. | ||
31 | </para> | 43 | </para> |
32 | </section> | 44 | </section> |
33 | 45 | ||
@@ -35,10 +47,27 @@ | |||
35 | <title>SDK Development Model</title> | 47 | <title>SDK Development Model</title> |
36 | 48 | ||
37 | <para> | 49 | <para> |
38 | * Development Model - provide a figure that shows the development | 50 | Fundamentally, the SDK fits into the development process as follows: |
39 | pieces using boxes and arrows. | 51 | <imagedata fileref="figures/sdk-environment.png" align="center" width="6in" depth="5in" scalefit="100" /> |
40 | Include all possible methods, inputs and outputs. | 52 | The SDK is installed on any machine and can be used to develop |
41 | <imagedata fileref="figures/sdk-environment.png" align="center" width="6in" depth="5in" scalefit="100" /> | 53 | applications, images, and kernels. |
54 | An SDK can even be used by a QA Engineer or Release Engineer. | ||
55 | The fundamental concept is that the machine that has the SDK installed | ||
56 | does not have to be associated with the machine that has the | ||
57 | Yocto Project installed. | ||
58 | A developer can independently compile and test an object on their | ||
59 | machine and then, when the object is ready for integration into an | ||
60 | image, they can simply make it available to the machine that has the | ||
61 | the Yocto Project. | ||
62 | Once the object is available, the image can be rebuilt using the | ||
63 | Yocto Project to produce the modified image. | ||
64 | </para> | ||
65 | |||
66 | <para> | ||
67 | The remainder of this manual describes how to use both the standard | ||
68 | SDK and the extensible SDK. | ||
69 | Information also exists in appendix form that describes how you can | ||
70 | build, install, and modify an SDK. | ||
42 | </para> | 71 | </para> |
43 | </section> | 72 | </section> |
44 | 73 | ||