summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-09-15 05:52:25 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-09-25 17:59:57 +0100
commitace70b31e99b5e0f22a89c8db3d444f3ba642369 (patch)
tree78cbb5d080f0e559ecf5ce70d8190c0eab6304fe
parent6d05d1799a8f7ca4c1525d3038b422d8540391c2 (diff)
downloadpoky-ace70b31e99b5e0f22a89c8db3d444f3ba642369.tar.gz
documentation/adt-manual/adt-prepare.xml: writer notes and section format
I added a couple of writer notes for development purposes. I also formated the section title references so they have quotes around them for easier reading in the PDF verison. (From yocto-docs rev: 37adb580cf6c1369da43fc4ef7aaa4cc1cee0e5c) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/adt-manual/adt-prepare.xml37
1 files changed, 27 insertions, 10 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 65ca6345ff..fd02696244 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -37,9 +37,10 @@
37 <filename>poky-edison-6.0</filename>. 37 <filename>poky-edison-6.0</filename>.
38 If you create a Git repository, then you can name the repository anything you like.</para> 38 If you create a Git repository, then you can name the repository anything you like.</para>
39 <para>You can find instruction on how to set up the Yocto Project files on your 39 <para>You can find instruction on how to set up the Yocto Project files on your
40 host development system by reading the 40 host development system by reading
41 <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html#getting-setup'> 41 the
42 Getting Setup</ulink> section in 42 "<ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html#getting-setup'>Getting
43 Setup</ulink>" section in
43 <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html'> 44 <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html'>
44 The Yocto Project Development Manual</ulink>.</para></listitem> 45 The Yocto Project Development Manual</ulink>.</para></listitem>
45 <listitem><para><emphasis>Yocto Project Build Tree:</emphasis> 46 <listitem><para><emphasis>Yocto Project Build Tree:</emphasis>
@@ -213,8 +214,8 @@
213 <note> 214 <note>
214 The ADT Installer requires the <filename>libtool</filename> package to complete. 215 The ADT Installer requires the <filename>libtool</filename> package to complete.
215 If you install the recommended packages as described in the 216 If you install the recommended packages as described in the
216 <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#packages'> 217 "<ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#packages'>Packages</ulink>"
217 Packages</ulink> section of 218 section of
218 <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html'> 219 <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html'>
219 The Yocto Project Quick Start</ulink>, then you will have libtool installed. 220 The Yocto Project Quick Start</ulink>, then you will have libtool installed.
220 </note> 221 </note>
@@ -254,7 +255,7 @@
254 <listitem><para>Go to 255 <listitem><para>Go to
255 <ulink url='http://autobuilder.yoctoproject.org/downloads/yocto-1.1/toolchain'></ulink> 256 <ulink url='http://autobuilder.yoctoproject.org/downloads/yocto-1.1/toolchain'></ulink>
256 and find the folder that matches your host development system 257 and find the folder that matches your host development system
257 (i.e. <filename>i686</filename> for 32-bit machines or 258 (i.e. <filename>i586</filename> for 32-bit machines or
258 <filename>x86_64</filename> for 64-bit machines).</para></listitem> 259 <filename>x86_64</filename> for 64-bit machines).</para></listitem>
259 <listitem><para>Go into that folder and download the toolchain tarball whose name 260 <listitem><para>Go into that folder and download the toolchain tarball whose name
260 includes the appropriate target architecture. 261 includes the appropriate target architecture.
@@ -262,7 +263,7 @@
262 you are going to use your cross-toolchain for an ARM-based target, go into the 263 you are going to use your cross-toolchain for an ARM-based target, go into the
263 <filename>x86_64</filename> folder and download the following tarball: 264 <filename>x86_64</filename> folder and download the following tarball:
264 <literallayout class='monospaced'> 265 <literallayout class='monospaced'>
265 yocto-eglibc-x86_64-arm-toolchain-gmae-1.1.tar.bz2 266 yocto-eglibc-x86_64-i586-toolchain-gmae-1.1.tar.bz2
266 </literallayout> 267 </literallayout>
267 <note>As an alternative to steps one and two, you can build the toolchain tarball 268 <note>As an alternative to steps one and two, you can build the toolchain tarball
268 if you have a Yocto Project build tree. 269 if you have a Yocto Project build tree.
@@ -329,7 +330,16 @@
329 330
330 <para> 331 <para>
331 After installing the toolchain, you must locate the target sysroot tarball and unpack 332 After installing the toolchain, you must locate the target sysroot tarball and unpack
332 it in a directory of your choice. 333 it in a directory of your choice.
334 </para>
335
336 <para>
337 WRITER'S NOTE: Right now I am a little fuzzy on just how you do this.
338 I am not sure if you just grab what is in <filename>build/tmp/deploy/images</filename>
339 and then unpack it with the <filename>tar -xjvf [tarball] [directory]</filename> or
340 if you have to run the tarball environment setup script found in
341 <filename>build/tmp</filename> and then run the
342 <filename>runqemu-extract-sdk [tarball] [directory]</filename> command.
333 </para> 343 </para>
334 </section> 344 </section>
335</section> 345</section>
@@ -369,8 +379,7 @@
369 hardware or the QEMU emulator. 379 hardware or the QEMU emulator.
370 That means you either have to build them or know where to get them. 380 That means you either have to build them or know where to get them.
371 You can find a quick example of how to build an image in the 381 You can find a quick example of how to build an image in the
372 <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#building-image'> 382 "<ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#building-image'>Building an Image</ulink>" section of
373 Building an Image</ulink> section of
374 <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html'> 383 <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html'>
375 The Yocto Project Quick Start</ulink>. 384 The Yocto Project Quick Start</ulink>.
376 <note><para> 385 <note><para>
@@ -390,6 +399,14 @@
390 The Yocto Project Reference Manual</ulink>.</para> 399 The Yocto Project Reference Manual</ulink>.</para>
391 </note> 400 </note>
392 </para> 401 </para>
402
403 <para>
404 WRITER'S NOTE: It seems to me that you need to take steps to unpack the image filesystem
405 at this point.
406 This would involve running the tarball environment setup script found in
407 <filename>build/tmp</filename> and then running the
408 <filename>runqemu-extract-sdk [tarball] [directory]</filename> command.
409 </para>
393</section> 410</section>
394 411
395</chapter> 412</chapter>