summaryrefslogtreecommitdiffstats
path: root/handbook/usingpoky.xml
diff options
context:
space:
mode:
authorYu Ke <ke.yu@intel.com>2010-09-09 10:34:34 +0800
committerRichard Purdie <rpurdie@linux.intel.com>2010-09-10 12:32:13 +0100
commit0a217cd18f09c837f67bf54956904a79fb013876 (patch)
treec080173ebcb98034b1809b17b092102ffbab9908 /handbook/usingpoky.xml
parent8627258ac3bae635c2ff54cfa24863e50a2a136c (diff)
downloadpoky-0a217cd18f09c837f67bf54956904a79fb013876.tar.gz
handbook: review and update CH1(introduction) and CH2(using Poky)
Signed-off-by: Yu Ke <ke.yu@intel.com> Signed-off-by: Kevin Tian <kevin.tian@intel.com>
Diffstat (limited to 'handbook/usingpoky.xml')
-rw-r--r--handbook/usingpoky.xml16
1 files changed, 14 insertions, 2 deletions
diff --git a/handbook/usingpoky.xml b/handbook/usingpoky.xml
index 07b8f6c939..50816c9273 100644
--- a/handbook/usingpoky.xml
+++ b/handbook/usingpoky.xml
@@ -118,15 +118,23 @@
118 </para> 118 </para>
119 <para> 119 <para>
120 <literallayout class='monospaced'> 120 <literallayout class='monospaced'>
121$ source poky-init-build-env 121$ source poky-init-build-env [build_dir]
122</literallayout> 122</literallayout>
123 </para> 123 </para>
124 <para> 124 <para>
125 The build_dir is the dir containing all the building object files. The default
126 build dir is poky-dir/build. Multiple build_dir can be used for different targets.
127 For example, ~/build/x86 for qemux86 target, and ~/build/arm for qemuarm target.
128 Please refer to <link linkend="structure-core-script">poky-init-build-env</link>
129 for detail info
130 </para>
131 <para>
125 Once the Poky build environment is set up, a target can now be built using: 132 Once the Poky build environment is set up, a target can now be built using:
126 </para> 133 </para>
127 <para> 134 <para>
128 <literallayout class='monospaced'> 135 <literallayout class='monospaced'>
129$ bitbake &lt;target&gt; 136$ bitbake &lt;target&gt;
137$ bitbake qemu-native
130</literallayout> 138</literallayout>
131 </para> 139 </para>
132 <para> 140 <para>
@@ -135,6 +143,8 @@ $ bitbake &lt;target&gt;
135 or the name of a recipe for a specific piece of software like 143 or the name of a recipe for a specific piece of software like
136 <application>busybox</application>. More details about the standard images 144 <application>busybox</application>. More details about the standard images
137 are available in the <link linkend='ref-images'>image reference section</link>. 145 are available in the <link linkend='ref-images'>image reference section</link>.
146 The qemu-native target will build the poky customized qemu, and will be used
147 by runqemu script later.
138 </para> 148 </para>
139</section> 149</section>
140 150
@@ -301,7 +311,7 @@ route add default gw 192.168.0.202 usb0
301 <para> 311 <para>
302 You can view a list of tasks in a given package by running 312 You can view a list of tasks in a given package by running
303 the listtasks task e.g. <command>bitbake matchbox-desktop -c 313 the listtasks task e.g. <command>bitbake matchbox-desktop -c
304 listtasks</command>. 314 listtasks</command>, and the result is in file ${WORKDIR}/temp/log.do_listtasks.pid.
305 </para> 315 </para>
306 </section> 316 </section>
307 317
@@ -317,6 +327,8 @@ route add default gw 192.168.0.202 usb0
317 directory. They show 327 directory. They show
318 which packages and tasks depend on which other packages and 328 which packages and tasks depend on which other packages and
319 tasks and are useful for debugging purposes. 329 tasks and are useful for debugging purposes.
330 <command>"bitbake -g -u depexp targetname"</command> will show result
331 in more human-readable GUI style.
320 </para> 332 </para>
321 </section> 333 </section>
322 334