diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-02-06 12:51:39 -0600 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-02-14 17:24:04 +0000 |
| commit | 0ad26c66e0b926591f5d68095bd4b142f381cd86 (patch) | |
| tree | ae8982295a2764d99a065c260d368ccdd50388f8 /documentation/dev-manual/dev-manual-newbie.xml | |
| parent | 3c984fdbc60600d5839a8c8d9042d8381d03d2af (diff) | |
| download | poky-0ad26c66e0b926591f5d68095bd4b142f381cd86.tar.gz | |
dev-manual: Updates to expose cross-toolchain recipes.
Added a bulleted list to the "Terms" section to help define
some toolchain recipes such as gcc-cross-initial,
gcc-cross-intermediate, and so forth.
Added a cross-reference link to the term
"Cross-Development Toolchain" in the the "Working Using
Stand-alone Cross-development Toolchains" section.
This gives the reader a way to see more on the toolchain
recipes.
(From yocto-docs rev: 2cb612424c0cf6addfd8bce8a0ef77665c35bd9a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/dev-manual-newbie.xml')
| -rw-r--r-- | documentation/dev-manual/dev-manual-newbie.xml | 58 |
1 files changed, 51 insertions, 7 deletions
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml index 169f3072ef..7c21379b99 100644 --- a/documentation/dev-manual/dev-manual-newbie.xml +++ b/documentation/dev-manual/dev-manual-newbie.xml | |||
| @@ -311,17 +311,61 @@ | |||
| 311 | variables for the Texas Instruments ARM Cortex-A8 development board). | 311 | variables for the Texas Instruments ARM Cortex-A8 development board). |
| 312 | Configuration files end with a <filename>.conf</filename> filename extension. | 312 | Configuration files end with a <filename>.conf</filename> filename extension. |
| 313 | </para></listitem> | 313 | </para></listitem> |
| 314 | <listitem><para><emphasis>Cross-Development Toolchain:</emphasis> | 314 | <listitem><para id='cross-development-toolchain'> |
| 315 | <emphasis>Cross-Development Toolchain:</emphasis> | ||
| 315 | A collection of software development | 316 | A collection of software development |
| 316 | tools and utilities that allow you to develop software for targeted architectures. | 317 | tools and utilities that allow you to develop software for |
| 317 | This toolchain contains cross-compilers, linkers, and debuggers that are specific to | 318 | targeted architectures. |
| 318 | an architecture. | 319 | This toolchain contains cross-compilers, linkers, and debuggers |
| 319 | You can use the OpenEmbedded build system to build a cross-development toolchain | 320 | that are specific to an architecture. |
| 320 | installer that when run installs the toolchain that contains the development tools you | 321 | You can use the OpenEmbedded build system to build a |
| 322 | cross-development toolchain installer that, when run, installs | ||
| 323 | the toolchain that contains the development tools you | ||
| 321 | need to cross-compile and test your software. | 324 | need to cross-compile and test your software. |
| 322 | The Yocto Project ships with images that contain installers for | 325 | The Yocto Project ships with images that contain installers for |
| 323 | toolchains for supported architectures as well. | 326 | toolchains for supported architectures as well. |
| 324 | Sometimes this toolchain is referred to as the meta-toolchain.</para></listitem> | 327 | Sometimes this toolchain is referred to as the |
| 328 | meta-toolchain.</para> | ||
| 329 | <para>Following is a list of toolchain recipes with brief | ||
| 330 | descriptions of each: | ||
| 331 | <itemizedlist> | ||
| 332 | <listitem><para><filename>gcc-cross-initial</filename>: | ||
| 333 | The initial compiler needed to bootstrap the toolchain | ||
| 334 | that runs on the host and is used to build software | ||
| 335 | for the target. | ||
| 336 | This tool is a 'native' package.</para></listitem> | ||
| 337 | <listitem><para><filename>gcc-cross-intermediate</filename>: | ||
| 338 | The second stage of the bootstrap process that runs | ||
| 339 | on the host and builds software for the target. | ||
| 340 | This tool is a 'native' package.</para></listitem> | ||
| 341 | <listitem><para><filename>gcc-cross</filename>: | ||
| 342 | The the final stage of the bootstrap process that | ||
| 343 | results in the cross compiler that runs on the host | ||
| 344 | and builds software for the target. | ||
| 345 | If you are replacing the cross compiler toolchain | ||
| 346 | with a custom version, this is what you must replace. | ||
| 347 | This tool is a 'native' package.</para></listitem> | ||
| 348 | <listitem><para><filename>gcc-runtime</filename>: | ||
| 349 | Runtime libraries from the toolchain bootstrapping | ||
| 350 | process. | ||
| 351 | This tool produces a binary for the target. | ||
| 352 | </para></listitem> | ||
| 353 | <listitem><para><filename>gcc-crosssdk-initial/intermediate</filename>: | ||
| 354 | Stage 1 and 2 of the a cross compiler that runs on the | ||
| 355 | host and builds for the SDK. | ||
| 356 | Often the SDK is not the same target as the host. | ||
| 357 | This tool is a 'native' binary.</para></listitem> | ||
| 358 | <listitem><para><filename>gcc-crosssdk</filename>: | ||
| 359 | The final stage of the SDK compiler. | ||
| 360 | This tool is a 'native' binary. | ||
| 361 | The tool runs on the host and builds for the SDK. | ||
| 362 | </para></listitem> | ||
| 363 | <listitem><para><filename>gcc-cross-canadian</filename>: | ||
| 364 | The compiler that runs on the SDK machine and is | ||
| 365 | included with the SDK that builds software for the | ||
| 366 | target. | ||
| 367 | This tool is a 'nativesdk' package.</para></listitem> | ||
| 368 | </itemizedlist></para></listitem> | ||
| 325 | <listitem><para><emphasis>Image:</emphasis> An image is the result produced when | 369 | <listitem><para><emphasis>Image:</emphasis> An image is the result produced when |
| 326 | BitBake processes a given collection of recipes and related metadata. | 370 | BitBake processes a given collection of recipes and related metadata. |
| 327 | Images are the binary output that run on specific hardware or QEMU | 371 | Images are the binary output that run on specific hardware or QEMU |
