diff options
Diffstat (limited to 'documentation/adt-manual/adt-prepare.rst')
-rw-r--r-- | documentation/adt-manual/adt-prepare.rst | 66 |
1 files changed, 33 insertions, 33 deletions
diff --git a/documentation/adt-manual/adt-prepare.rst b/documentation/adt-manual/adt-prepare.rst index eea12ec0c8..12b1e7918c 100644 --- a/documentation/adt-manual/adt-prepare.rst +++ b/documentation/adt-manual/adt-prepare.rst | |||
@@ -284,7 +284,7 @@ Follow these steps to generate the toolchain into the Build Directory: | |||
284 | Directory <&YOCTO_DOCS_DEV_URL;#source-directory>`__. | 284 | Directory <&YOCTO_DOCS_DEV_URL;#source-directory>`__. |
285 | 285 | ||
286 | 2. *Check your Local Configuration File:* At this point, you should be | 286 | 2. *Check your Local Configuration File:* At this point, you should be |
287 | sure that the ```MACHINE`` <&YOCTO_DOCS_REF_URL;#var-MACHINE>`__ | 287 | sure that the :term:`MACHINE` |
288 | variable in the ``local.conf`` file found in the ``conf`` directory | 288 | variable in the ``local.conf`` file found in the ``conf`` directory |
289 | of the Build Directory is set for the target architecture. Comments | 289 | of the Build Directory is set for the target architecture. Comments |
290 | within the ``local.conf`` file list the values you can use for the | 290 | within the ``local.conf`` file list the values you can use for the |
@@ -345,45 +345,45 @@ setup script for a 64-bit IA-based architecture installed in the default | |||
345 | installation directory would be the following: | 345 | installation directory would be the following: |
346 | YOCTO_ADTPATH_DIR/environment-setup-x86_64-poky-linux When you run the | 346 | YOCTO_ADTPATH_DIR/environment-setup-x86_64-poky-linux When you run the |
347 | setup script, many environment variables are defined: | 347 | setup script, many environment variables are defined: |
348 | ```SDKTARGETSYSROOT`` <&YOCTO_DOCS_REF_URL;#var-SDKTARGETSYSROOT>`__ - | 348 | :term:`SDKTARGETSYSROOT` - |
349 | The path to the sysroot used for cross-compilation | 349 | The path to the sysroot used for cross-compilation |
350 | ```PKG_CONFIG_PATH`` <&YOCTO_DOCS_REF_URL;#var-PKG_CONFIG_PATH>`__ - The | 350 | :term:`PKG_CONFIG_PATH` - The |
351 | path to the target pkg-config files | 351 | path to the target pkg-config files |
352 | ```CONFIG_SITE`` <&YOCTO_DOCS_REF_URL;#var-CONFIG_SITE>`__ - A GNU | 352 | :term:`CONFIG_SITE` - A GNU |
353 | autoconf site file preconfigured for the target | 353 | autoconf site file preconfigured for the target |
354 | ```CC`` <&YOCTO_DOCS_REF_URL;#var-CC>`__ - The minimal command and | 354 | :term:`CC` - The minimal command and |
355 | arguments to run the C compiler | 355 | arguments to run the C compiler |
356 | ```CXX`` <&YOCTO_DOCS_REF_URL;#var-CXX>`__ - The minimal command and | 356 | :term:`CXX` - The minimal command and |
357 | arguments to run the C++ compiler | 357 | arguments to run the C++ compiler |
358 | ```CPP`` <&YOCTO_DOCS_REF_URL;#var-CPP>`__ - The minimal command and | 358 | :term:`CPP` - The minimal command and |
359 | arguments to run the C preprocessor | 359 | arguments to run the C preprocessor |
360 | ```AS`` <&YOCTO_DOCS_REF_URL;#var-AS>`__ - The minimal command and | 360 | :term:`AS` - The minimal command and |
361 | arguments to run the assembler ```LD`` <&YOCTO_DOCS_REF_URL;#var-LD>`__ | 361 | arguments to run the assembler :term:`LD` |
362 | - The minimal command and arguments to run the linker | 362 | - The minimal command and arguments to run the linker |
363 | ```GDB`` <&YOCTO_DOCS_REF_URL;#var-GDB>`__ - The minimal command and | 363 | :term:`GDB` - The minimal command and |
364 | arguments to run the GNU Debugger | 364 | arguments to run the GNU Debugger |
365 | ```STRIP`` <&YOCTO_DOCS_REF_URL;#var-STRIP>`__ - The minimal command and | 365 | :term:`STRIP` - The minimal command and |
366 | arguments to run 'strip', which strips symbols | 366 | arguments to run 'strip', which strips symbols |
367 | ```RANLIB`` <&YOCTO_DOCS_REF_URL;#var-RANLIB>`__ - The minimal command | 367 | :term:`RANLIB` - The minimal command |
368 | and arguments to run 'ranlib' | 368 | and arguments to run 'ranlib' |
369 | ```OBJCOPY`` <&YOCTO_DOCS_REF_URL;#var-OBJCOPY>`__ - The minimal command | 369 | :term:`OBJCOPY` - The minimal command |
370 | and arguments to run 'objcopy' | 370 | and arguments to run 'objcopy' |
371 | ```OBJDUMP`` <&YOCTO_DOCS_REF_URL;#var-OBJDUMP>`__ - The minimal command | 371 | :term:`OBJDUMP` - The minimal command |
372 | and arguments to run 'objdump' ```AR`` <&YOCTO_DOCS_REF_URL;#var-AR>`__ | 372 | and arguments to run 'objdump' :term:`AR` |
373 | - The minimal command and arguments to run 'ar' | 373 | - The minimal command and arguments to run 'ar' |
374 | ```NM`` <&YOCTO_DOCS_REF_URL;#var-NM>`__ - The minimal command and | 374 | :term:`NM` - The minimal command and |
375 | arguments to run 'nm' | 375 | arguments to run 'nm' |
376 | ```TARGET_PREFIX`` <&YOCTO_DOCS_REF_URL;#var-TARGET_PREFIX>`__ - The | 376 | :term:`TARGET_PREFIX` - The |
377 | toolchain binary prefix for the target tools | 377 | toolchain binary prefix for the target tools |
378 | ```CROSS_COMPILE`` <&YOCTO_DOCS_REF_URL;#var-CROSS_COMPILE>`__ - The | 378 | :term:`CROSS_COMPILE` - The |
379 | toolchain binary prefix for the target tools | 379 | toolchain binary prefix for the target tools |
380 | ```CONFIGURE_FLAGS`` <&YOCTO_DOCS_REF_URL;#var-CONFIGURE_FLAGS>`__ - The | 380 | :term:`CONFIGURE_FLAGS` - The |
381 | minimal arguments for GNU configure | 381 | minimal arguments for GNU configure |
382 | ```CFLAGS`` <&YOCTO_DOCS_REF_URL;#var-CFLAGS>`__ - Suggested C flags | 382 | :term:`CFLAGS` - Suggested C flags |
383 | ```CXXFLAGS`` <&YOCTO_DOCS_REF_URL;#var-CXXFLAGS>`__ - Suggested C++ | 383 | :term:`CXXFLAGS` - Suggested C++ |
384 | flags ```LDFLAGS`` <&YOCTO_DOCS_REF_URL;#var-LDFLAGS>`__ - Suggested | 384 | flags :term:`LDFLAGS` - Suggested |
385 | linker flags when you use CC to link | 385 | linker flags when you use CC to link |
386 | ```CPPFLAGS`` <&YOCTO_DOCS_REF_URL;#var-CPPFLAGS>`__ - Suggested | 386 | :term:`CPPFLAGS` - Suggested |
387 | preprocessor flags | 387 | preprocessor flags |
388 | 388 | ||
389 | Securing Kernel and Filesystem Images | 389 | Securing Kernel and Filesystem Images |
@@ -411,7 +411,7 @@ that you can use unaltered in the QEMU emulator. These kernel images | |||
411 | reside in the release area - ` <&YOCTO_MACHINES_DL_URL;>`__ and are | 411 | reside in the release area - ` <&YOCTO_MACHINES_DL_URL;>`__ and are |
412 | ideal for experimentation using Yocto Project. For information on the | 412 | ideal for experimentation using Yocto Project. For information on the |
413 | image types you can build using the OpenEmbedded build system, see the | 413 | image types you can build using the OpenEmbedded build system, see the |
414 | "`Images <&YOCTO_DOCS_REF_URL;#ref-images>`__" chapter in the Yocto | 414 | ":ref:`ref-manual/ref-images:Images`" chapter in the Yocto |
415 | Project Reference Manual. | 415 | Project Reference Manual. |
416 | 416 | ||
417 | If you are planning on developing against your image and you are not | 417 | If you are planning on developing against your image and you are not |
@@ -434,7 +434,7 @@ this by including the ``eclipse-debug`` image feature. | |||
434 | To include the ``eclipse-debug`` image feature, modify your | 434 | To include the ``eclipse-debug`` image feature, modify your |
435 | ``local.conf`` file in the `Build | 435 | ``local.conf`` file in the `Build |
436 | Directory <&YOCTO_DOCS_DEV_URL;#build-directory>`__ so that the | 436 | Directory <&YOCTO_DOCS_DEV_URL;#build-directory>`__ so that the |
437 | ```EXTRA_IMAGE_FEATURES`` <&YOCTO_DOCS_REF_URL;#var-EXTRA_IMAGE_FEATURES>`__ | 437 | :term:`EXTRA_IMAGE_FEATURES` |
438 | variable includes the "eclipse-debug" feature. After modifying the | 438 | variable includes the "eclipse-debug" feature. After modifying the |
439 | configuration file, you can rebuild the image. Once the image is | 439 | configuration file, you can rebuild the image. Once the image is |
440 | rebuilt, the ``tcf-agent`` will be included in the image and is launched | 440 | rebuilt, the ``tcf-agent`` will be included in the image and is launched |
@@ -513,8 +513,8 @@ Another feature is that only one set of cross-canadian toolchain | |||
513 | binaries are produced per architecture. This feature takes advantage of | 513 | binaries are produced per architecture. This feature takes advantage of |
514 | the fact that the target hardware can be passed to ``gcc`` as a set of | 514 | the fact that the target hardware can be passed to ``gcc`` as a set of |
515 | compiler options. Those options are set up by the environment script and | 515 | compiler options. Those options are set up by the environment script and |
516 | contained in variables such as ```CC`` <&YOCTO_DOCS_REF_URL;#var-CC>`__ | 516 | contained in variables such as :term:`CC` |
517 | and ```LD`` <&YOCTO_DOCS_REF_URL;#var-LD>`__. This reduces the space | 517 | and :term:`LD`. This reduces the space |
518 | needed for the tools. Understand, however, that a sysroot is still | 518 | needed for the tools. Understand, however, that a sysroot is still |
519 | needed for every target since those binaries are target-specific. | 519 | needed for every target since those binaries are target-specific. |
520 | 520 | ||
@@ -524,9 +524,9 @@ environment setup script (i.e. | |||
524 | ```oe-init-build-env-memres`` <&YOCTO_DOCS_REF_URL;#structure-memres-core-script>`__) | 524 | ```oe-init-build-env-memres`` <&YOCTO_DOCS_REF_URL;#structure-memres-core-script>`__) |
525 | located in the Source Directory and you must make sure your | 525 | located in the Source Directory and you must make sure your |
526 | ``conf/local.conf`` variables are correct. In particular, you need to be | 526 | ``conf/local.conf`` variables are correct. In particular, you need to be |
527 | sure the ```MACHINE`` <&YOCTO_DOCS_REF_URL;#var-MACHINE>`__ variable | 527 | sure the :term:`MACHINE` variable |
528 | matches the architecture for which you are building and that the | 528 | matches the architecture for which you are building and that the |
529 | ```SDKMACHINE`` <&YOCTO_DOCS_REF_URL;#var-SDKMACHINE>`__ variable is | 529 | :term:`SDKMACHINE` variable is |
530 | correctly set if you are building a toolchain designed to run on an | 530 | correctly set if you are building a toolchain designed to run on an |
531 | architecture that differs from your current development host machine | 531 | architecture that differs from your current development host machine |
532 | (i.e. the build machine). | 532 | (i.e. the build machine). |
@@ -565,10 +565,10 @@ follows: | |||
565 | 565 | ||
566 | - Make sure you add the layer that contains the toolchain to your | 566 | - Make sure you add the layer that contains the toolchain to your |
567 | ``bblayers.conf`` file through the | 567 | ``bblayers.conf`` file through the |
568 | ```BBLAYERS`` <&YOCTO_DOCS_REF_URL;#var-BBLAYERS>`__ variable. | 568 | :term:`BBLAYERS` variable. |
569 | 569 | ||
570 | - Set the | 570 | - Set the |
571 | ```EXTERNAL_TOOLCHAIN`` <&YOCTO_DOCS_REF_URL;#var-EXTERNAL_TOOLCHAIN>`__ | 571 | :term:`EXTERNAL_TOOLCHAIN` |
572 | variable in your ``local.conf`` file to the location in which you | 572 | variable in your ``local.conf`` file to the location in which you |
573 | installed the toolchain. | 573 | installed the toolchain. |
574 | 574 | ||
@@ -577,7 +577,7 @@ Mentor Graphics Sourcery G++ Toolchain. You can see information on how | |||
577 | to use that particular layer in the ``README`` file at | 577 | to use that particular layer in the ``README`` file at |
578 | ` <http://github.com/MentorEmbedded/meta-sourcery/>`__. You can find | 578 | ` <http://github.com/MentorEmbedded/meta-sourcery/>`__. You can find |
579 | further information by reading about the | 579 | further information by reading about the |
580 | ```TCMODE`` <&YOCTO_DOCS_REF_URL;#var-TCMODE>`__ variable in the Yocto | 580 | :term:`TCMODE` variable in the Yocto |
581 | Project Reference Manual's variable glossary. | 581 | Project Reference Manual's variable glossary. |
582 | 582 | ||
583 | .. _using-pre-built: | 583 | .. _using-pre-built: |
@@ -712,7 +712,7 @@ core-image-profile-qemuarch.ext3 core-image-profile-qemuarch.tar.bz2 | |||
712 | Where: profile is the filesystem image's profile: lsb, lsb-dev, lsb-sdk, | 712 | Where: profile is the filesystem image's profile: lsb, lsb-dev, lsb-sdk, |
713 | lsb-qt3, minimal, minimal-dev, sato, sato-dev, or sato-sdk. For | 713 | lsb-qt3, minimal, minimal-dev, sato, sato-dev, or sato-sdk. For |
714 | information on these types of image profiles, see the | 714 | information on these types of image profiles, see the |
715 | "`Images <&YOCTO_DOCS_REF_URL;#ref-images>`__" chapter in the Yocto | 715 | ":ref:`ref-manual/ref-images:Images`" chapter in the Yocto |
716 | Project Reference Manual. arch is a string representing the target | 716 | Project Reference Manual. arch is a string representing the target |
717 | architecture: x86, x86-64, ppc, mips, or arm. | 717 | architecture: x86, x86-64, ppc, mips, or arm. |
718 | 718 | ||