diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-01-19 12:52:27 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-01-30 16:05:59 +0000 |
commit | 257dbe8d39a6b530abc883086024604a0bd59b64 (patch) | |
tree | ebb1f8f1b9d706253a668afcc6e4d4570d2e4d3a /documentation/adt-manual/adt-prepare.xml | |
parent | c81c4cb0c7c5905d2b8bf231205879d8a5bf87b5 (diff) | |
download | poky-257dbe8d39a6b530abc883086024604a0bd59b64.tar.gz |
documentation/adt-manual/adt-prepare.xml: Updates for 1.1.1
These changes reflect working through the chapter using the
1.1.1 release. Several areas needed tweaking.
(From yocto-docs rev: 566b8a492e502e88a1404f833db140a6408da592)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/adt-manual/adt-prepare.xml')
-rw-r--r-- | documentation/adt-manual/adt-prepare.xml | 50 |
1 files changed, 27 insertions, 23 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml index b45da5f6c2..79c44849e9 100644 --- a/documentation/adt-manual/adt-prepare.xml +++ b/documentation/adt-manual/adt-prepare.xml | |||
@@ -100,7 +100,7 @@ | |||
100 | a top-level directory named <filename>adt-installer</filename>: | 100 | a top-level directory named <filename>adt-installer</filename>: |
101 | <literallayout class='monospaced'> | 101 | <literallayout class='monospaced'> |
102 | $ cd ~ | 102 | $ cd ~ |
103 | $ cp ~/poky/build/tmp/deploy/sdk/adt_installer.tar.bz2 $HOME | 103 | $ cp ~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2 $HOME |
104 | $ tar -xjf adt_installer.tar.bz2 | 104 | $ tar -xjf adt_installer.tar.bz2 |
105 | </literallayout> | 105 | </literallayout> |
106 | Unpacking it creates the directory <filename>adt-installer</filename>, | 106 | Unpacking it creates the directory <filename>adt-installer</filename>, |
@@ -165,9 +165,10 @@ | |||
165 | 165 | ||
166 | <para> | 166 | <para> |
167 | After you have configured the <filename>adt_installer.conf</filename> file, | 167 | After you have configured the <filename>adt_installer.conf</filename> file, |
168 | run the installer using the following command: | 168 | run the installer for this example using the following commands: |
169 | <literallayout class='monospaced'> | 169 | <literallayout class='monospaced'> |
170 | $ adt_installer | 170 | $ cd ~/adt-installer |
171 | $ ./adt_installer | ||
171 | </literallayout> | 172 | </literallayout> |
172 | </para> | 173 | </para> |
173 | 174 | ||
@@ -214,9 +215,9 @@ | |||
214 | Follow these steps: | 215 | Follow these steps: |
215 | <orderedlist> | 216 | <orderedlist> |
216 | <listitem><para>Go to | 217 | <listitem><para>Go to |
217 | <ulink url='http://www.yoctoproject.org/downloads/yocto-1.1.1/toolchain'></ulink> | 218 | <ulink url='http://downloads.yoctoproject.org/releases/yocto/yocto-1.1.1/toolchain'></ulink> |
218 | and find the folder that matches your host development system | 219 | and find the folder that matches your host development system |
219 | (i.e. <filename>i586</filename> for 32-bit machines or | 220 | (i.e. <filename>i686</filename> for 32-bit machines or |
220 | <filename>x86_64</filename> for 64-bit machines).</para></listitem> | 221 | <filename>x86_64</filename> for 64-bit machines).</para></listitem> |
221 | <listitem><para>Go into that folder and download the toolchain tarball whose name | 222 | <listitem><para>Go into that folder and download the toolchain tarball whose name |
222 | includes the appropriate target architecture. | 223 | includes the appropriate target architecture. |
@@ -224,7 +225,7 @@ | |||
224 | you are going to use your cross-toolchain for an Intel-based 32-bit target, go into the | 225 | you are going to use your cross-toolchain for an Intel-based 32-bit target, go into the |
225 | <filename>x86_64</filename> folder and download the following tarball: | 226 | <filename>x86_64</filename> folder and download the following tarball: |
226 | <literallayout class='monospaced'> | 227 | <literallayout class='monospaced'> |
227 | yocto-eglibc-x86_64-i586-toolchain-1.1.tar.bz2 | 228 | poky-eglibc-x86_64-i586-toolchain-1.1.1.tar.bz2 |
228 | </literallayout> | 229 | </literallayout> |
229 | <note><para>As an alternative to steps one and two, you can build the toolchain tarball | 230 | <note><para>As an alternative to steps one and two, you can build the toolchain tarball |
230 | if you have a Yocto Project build tree. | 231 | if you have a Yocto Project build tree. |
@@ -244,6 +245,12 @@ | |||
244 | The tarball expands into <filename>/opt/poky/1.1.1</filename>. | 245 | The tarball expands into <filename>/opt/poky/1.1.1</filename>. |
245 | Once the tarball is expanded, the cross-toolchain is installed. | 246 | Once the tarball is expanded, the cross-toolchain is installed. |
246 | You will notice environment setup files for the cross-toolchain in the directory. | 247 | You will notice environment setup files for the cross-toolchain in the directory. |
248 | Here is an example where the tarball exists in the user's <filename>Downloads</filename> | ||
249 | directory: | ||
250 | <literallayout class='monospaced'> | ||
251 | # cd / | ||
252 | # tar -xjf /home/scottrif/Downloads/poky-eglibc-x86_64-i586-toolchain-gmae-1.1.tar.bz2 | ||
253 | </literallayout> | ||
247 | </para></listitem> | 254 | </para></listitem> |
248 | </orderedlist> | 255 | </orderedlist> |
249 | </para> | 256 | </para> |
@@ -280,7 +287,7 @@ | |||
280 | command.</note></para></listitem> | 287 | command.</note></para></listitem> |
281 | <listitem><para>Run <filename>bitbake meta-ide-support</filename> to complete the | 288 | <listitem><para>Run <filename>bitbake meta-ide-support</filename> to complete the |
282 | cross-toolchain installation. | 289 | cross-toolchain installation. |
283 | <note>If change out of your working directory after you | 290 | <note>If you change out of your working directory after you |
284 | <filename>source</filename> the environment setup script and before you run | 291 | <filename>source</filename> the environment setup script and before you run |
285 | the <filename>bitbake</filename> command, the command might not work. | 292 | the <filename>bitbake</filename> command, the command might not work. |
286 | Be sure to run the <filename>bitbake</filename> command immediately | 293 | Be sure to run the <filename>bitbake</filename> command immediately |
@@ -311,14 +318,14 @@ | |||
311 | </para> | 318 | </para> |
312 | 319 | ||
313 | <para> | 320 | <para> |
314 | Be sure to run the environment setup script that matches the architecture for | 321 | Be sure to source the environment setup script that matches the architecture for |
315 | which you are developing. | 322 | which you are developing. |
316 | Environment setup scripts begin with the string “<filename>environment-setup</filename>” | 323 | Environment setup scripts begin with the string “<filename>environment-setup</filename>” |
317 | and include as part of their name the architecture. | 324 | and include as part of their name the architecture. |
318 | For example, the toolchain environment setup script for a 64-bit IA-based architecture would | 325 | For example, the command to source the toolchain environment setup script |
319 | be the following: | 326 | for a 64-bit IA-based machine would be the following: |
320 | <literallayout class='monospaced'> | 327 | <literallayout class='monospaced'> |
321 | /opt/poky/1.1.1/environment-setup-x86_64-poky-linux | 328 | $ source /opt/poky/1.1.1/environment-setup-x86_64-poky-linux |
322 | </literallayout> | 329 | </literallayout> |
323 | </para> | 330 | </para> |
324 | </section> | 331 | </section> |
@@ -341,9 +348,7 @@ | |||
341 | pre-built versions. | 348 | pre-built versions. |
342 | You can find examples for both these situations in the | 349 | You can find examples for both these situations in the |
343 | "<ulink url='http://www.yoctoproject.org/docs/1.1.1/yocto-project-qs/yocto-project-qs.html#test-run'>A | 350 | "<ulink url='http://www.yoctoproject.org/docs/1.1.1/yocto-project-qs/yocto-project-qs.html#test-run'>A |
344 | Quick Test Run</ulink>" section of | 351 | Quick Test Run</ulink>" section of The Yocto Project Quick Start. |
345 | <ulink url='http://www.yoctoproject.org/docs/1.1.1/yocto-project-qs/yocto-project-qs.html'> | ||
346 | The Yocto Project Quick Start</ulink>. | ||
347 | </para> | 352 | </para> |
348 | 353 | ||
349 | <para> | 354 | <para> |
@@ -352,12 +357,10 @@ | |||
352 | <filename>mips</filename>, <filename>powerpc</filename>, and <filename>arm</filename>) | 357 | <filename>mips</filename>, <filename>powerpc</filename>, and <filename>arm</filename>) |
353 | that you can use unaltered in the QEMU emulator. | 358 | that you can use unaltered in the QEMU emulator. |
354 | These kernel images reside in the Yocto Project release | 359 | These kernel images reside in the Yocto Project release |
355 | area - <ulink url='http://www.yoctoproject.org/downloads/yocto-1.1.1/machines/'></ulink> | 360 | area - <ulink url='http://downloads.yoctoproject.org/releases/yocto/yocto-1.1.1/machines/'></ulink> |
356 | and are ideal for experimentation within Yocto Project. | 361 | and are ideal for experimentation within Yocto Project. |
357 | For information on the image types you can build using the Yocto Project, see the | 362 | For information on the image types you can build using the Yocto Project, see the |
358 | "<ulink url='http://www.yoctoproject.org/docs/1.1.1/poky-ref-manual/poky-ref-manual.html#ref-images'>Reference: Images</ulink>" appendix in | 363 | "<ulink url='http://www.yoctoproject.org/docs/1.1.1/poky-ref-manual/poky-ref-manual.html#ref-images'>Reference: Images</ulink>" appendix in The Yocto Project Reference Manual. |
359 | <ulink url='http://www.yoctoproject.org/docs/1.1.1/poky-ref-manual/poky-ref-manual.html'> | ||
360 | The Yocto Project Reference Manual</ulink>. | ||
361 | </para> | 364 | </para> |
362 | 365 | ||
363 | <para> | 366 | <para> |
@@ -373,7 +376,7 @@ | |||
373 | If you want to use a different image type that contains the <filename>tcf-agent</filename>, | 376 | If you want to use a different image type that contains the <filename>tcf-agent</filename>, |
374 | you can do so one of two ways: | 377 | you can do so one of two ways: |
375 | <itemizedlist> | 378 | <itemizedlist> |
376 | <listitem><para>Modify the <filename>conf/local.conf</filename> configuration in | 379 | <listitem><para>Modify the <filename>conf/local.conf</filename> configuration file in |
377 | the Yocto Project build directory and then rebuild the image. | 380 | the Yocto Project build directory and then rebuild the image. |
378 | With this method, you need to modify the <filename>EXTRA_IMAGE_FEATURES</filename> | 381 | With this method, you need to modify the <filename>EXTRA_IMAGE_FEATURES</filename> |
379 | variable to have the value of "tools-debug" before rebuilding the image. | 382 | variable to have the value of "tools-debug" before rebuilding the image. |
@@ -429,16 +432,17 @@ | |||
429 | To extract the root filesystem, first <filename>source</filename> | 432 | To extract the root filesystem, first <filename>source</filename> |
430 | the cross-development environment setup script and then | 433 | the cross-development environment setup script and then |
431 | use the <filename>runqemu-extract-sdk</filename> command on the | 434 | use the <filename>runqemu-extract-sdk</filename> command on the |
432 | filesystem image. | 435 | filesystem image tarball. |
433 | For example, the following commands set up the environment and then extract | 436 | For example, the following commands set up the environment by sourcing |
437 | the setup script from within the build directory and then extracting | ||
434 | the root filesystem from a previously built filesystem image tarball named | 438 | the root filesystem from a previously built filesystem image tarball named |
435 | <filename>core-image-sato-sdk-qemux86-2011091411831.rootfs.tar.bz2</filename>. | 439 | <filename>core-image-sato-sdk-qemux86.tar.bz2</filename>. |
436 | The example extracts the root filesystem into the <filename>$HOME/qemux86-sato</filename> | 440 | The example extracts the root filesystem into the <filename>$HOME/qemux86-sato</filename> |
437 | directory: | 441 | directory: |
438 | <literallayout class='monospaced'> | 442 | <literallayout class='monospaced'> |
439 | $ source $HOME/poky/build/tmp/environment-setup-i586-poky-linux | 443 | $ source $HOME/poky/build/tmp/environment-setup-i586-poky-linux |
440 | $ runqemu-extract-sdk \ | 444 | $ runqemu-extract-sdk \ |
441 | tmp/deploy/images/core-image-sato-sdk-qemux86-2011091411831.rootfs.tar.bz2 \ | 445 | tmp/deploy/images/core-image-sato-sdk-qemux86.tar.bz2 \ |
442 | $HOME/qemux86-sato | 446 | $HOME/qemux86-sato |
443 | </literallayout> | 447 | </literallayout> |
444 | In this case, you could now point to the target sysroot at | 448 | In this case, you could now point to the target sysroot at |