blob: a04164a413310587cb547806a8b6eed407c5010b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
|
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
[<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] >
<chapter id='sdk-extensible'>
<title>Using the Extensible SDK</title>
<para>
This chapter describes what you need on your machine in order to use
an extensible SDK.
The chapter does not repeat information that also applies to using the
standard SDK.
The chapter also includes procedures of tasks you can perform using
an extensible SDK.
<note>
The tasks you can perform using a standard SDK are also available
using an extensible SDK.
For information on using the standard SDK, see the
"<link linkend='sdk-using-the-standard-sdk'>Using the Standard SDK</link>"
chapter.
</note>
</para>
<section id='sdk-setting-up-to-use-the-extensible-sdk'>
<title>Setting Up to Use the Extensible SDK</title>
<para>
Here is a list of items I think need addressed in this section:
<itemizedlist>
<listitem><para><emphasis>Cover differences in the development
that might be impacted because they are using an extensible
SDK</emphasis></para>
<para>Presumably, the various development scenarios are
covered regarding setup in the previous chapter.
Are these impacted because the developer is going to now be
using an extensible SDK?
If so, what are the implications?
</para></listitem>
<listitem><para><emphasis>What new recommendations exist now that
the developer is going to be using an extensible SDK?</emphasis></para>
<para>We should cover the most common development scenarios
that apply when using an extensible SDK.
Is there a recommended development flow we want to present
when using an extensible SDK?
What conditions in a development scenario warrant use of
the extensible SDK as compared to the standard SDK?
</para></listitem>
<listitem><para><emphasis>What procedures do we want to cover to set
up the extensible SDK?</emphasis></para>
<para>Is it just a matter of building out the SDK using
<filename>bitbake -c populate_sdk_ext</filename>?
Is there a pre-built extensible SDK laying around they can
find and download if they are using a machine that does not
have YP installed, which would prevent them from building their
own SDK?
</para></listitem>
</itemizedlist>
</para>
</section>
<section id='sdk-using-the-extensible-sdk-to-task-1'>
<title>Using the Extensible SDK to <replaceable>item 1</replaceable></title>
<para>
Describe the specific task you are going to accomplish with the
extensible SDK.
Provide a diagram showing the rough flow of the task.
Provide specific steps using a real example that works through the
task.
</para>
</section>
<section id='sdk-using-the-extensible-sdk-to-task-2'>
<title>Using the Extensible SDK to <replaceable>item-2</replaceable></title>
<para>
Describe the specific task you are going to accomplish with the
extensible SDK.
Provide a diagram showing the rough flow of the task.
Provide specific steps using a real example that works through the
task.
</para>
</section>
<section id='sdk-using-the-extensible-sdk-to-task-3'>
<title>Using the Extensible SDK to <replaceable>item-3</replaceable></title>
<para>
Describe the specific task you are going to accomplish with the
extensible SDK.
Provide a diagram showing the rough flow of the task.
Provide specific steps using a real example that works through the
task.
</para>
</section>
<section id='sdk-using-the-extensible-sdk-to-task-x'>
<title>Using the Extensible SDK to <replaceable>item-x</replaceable></title>
<para>
Describe the specific task you are going to accomplish with the
extensible SDK.
Provide a diagram showing the rough flow of the task.
Provide specific steps using a real example that works through the
task.
</para>
</section>
</chapter>
<!--
vim: expandtab tw=80 ts=4
-->
|
