diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2011-07-27 13:29:36 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-08-04 15:06:49 +0100 |
| commit | ebf03998910f5c39ed827dc95c692218dd400d30 (patch) | |
| tree | 3f7ba9b5aadaf31e8131366525a615e0c435c50b /documentation/dev-manual/dev-manual-model.xml | |
| parent | 0bea49d340b66a2bf93687c14e5b4aaf36367210 (diff) | |
| download | poky-ebf03998910f5c39ed827dc95c692218dd400d30.tar.gz | |
documentation/dev-manual: Added reference to example appendices
In dev-manual-model.xml I included two references: one to the
BSP Development Example and one to the Kernel Modification Example.
I had to add the target "id" stuff to both dev-manual-bsp-appendix.xml
and dev-manual-model.xml
(From yocto-docs rev: bcae1e723610e1769f0a524e3c1d9918c7cb1061)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/dev-manual-model.xml')
| -rw-r--r-- | documentation/dev-manual/dev-manual-model.xml | 27 |
1 files changed, 4 insertions, 23 deletions
diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index 6b60b4c426..b07fe500a8 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml | |||
| @@ -6,20 +6,6 @@ | |||
| 6 | <title>Common Development Models</title> | 6 | <title>Common Development Models</title> |
| 7 | 7 | ||
| 8 | <para> | 8 | <para> |
| 9 | [WRITERS NOTE: This chapter presents common development models within the Yocto Project. | ||
| 10 | Reading this chapter will give the user a feel for the overall development process. | ||
| 11 | The chapter will follow the framework for the manual. | ||
| 12 | The team decided to present a single development model and not to try and represent all the | ||
| 13 | various possibilities that might exist. | ||
| 14 | The chapter will include an over-arching diagram that shows a simple, most-common development model. | ||
| 15 | The diagram will consist of boxes that represent high-level areas of the development process. | ||
| 16 | For example, a box for “Setting Up” will be in the model. | ||
| 17 | A box for “Debugging” will exist. | ||
| 18 | The diagram needs to account for the two use-cases we are going to showcase | ||
| 19 | (system development and application development)]. | ||
| 20 | </para> | ||
| 21 | |||
| 22 | <para> | ||
| 23 | Many development models exist for which you can use the Yocto Project. | 9 | Many development models exist for which you can use the Yocto Project. |
| 24 | However, for the purposes of this manual we are going to focus on two common ones: | 10 | However, for the purposes of this manual we are going to focus on two common ones: |
| 25 | System Development and User Application Development. | 11 | System Development and User Application Development. |
| @@ -29,15 +15,10 @@ | |||
| 29 | </para> | 15 | </para> |
| 30 | 16 | ||
| 31 | <para> | 17 | <para> |
| 32 | This chapter presents an overview of the primary models. | 18 | This chapter presents overviews of both system and application models. |
| 33 | Supsequent appendices in the manual provide detailed explanations of the examples. | 19 | If you want to reference specific examples of these development models, |
| 34 | </para> | 20 | see <xref linkend='dev-manual-bsp-appendix'>BSP Development Example</xref> and |
| 35 | 21 | <xref linkend='dev-manual-kernel-appendix'>Kernel Modification Example</xref>. | |
| 36 | <para> | ||
| 37 | [WRITERS NOTE: What is undetermined at this point is how much of the entire development process | ||
| 38 | we include in this particular chapter. | ||
| 39 | In other words, do we cover debugging and emulation steps here on a case-specific basis? | ||
| 40 | Or, do we capture that information in the appropriate subsequent chapter by case?] | ||
| 41 | </para> | 22 | </para> |
| 42 | 23 | ||
| 43 | <section id='system-development-model'> | 24 | <section id='system-development-model'> |
