mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-31 00:39:46 +00:00
Code Issues Projects Releases Wiki Activity

documentation/poky-ref-manual/development.xml: Removed toolchain dev section

Browse Source 
The section "External Development Using the Meta-Toolchain" was removed.
The information in this section is better presented in the ADT manual
and in the YP Development manual.

(From yocto-docs rev: 2488d6ac9872b00a8887a12a6c77aa16d30ad5e4)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2012-06-11 14:17:02 -07:00
committed by Richard Purdie
parent 91911f600f
commit fa332a5b27
1 changed files with 0 additions and 50 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/poky-ref-manual/development.xml
-50
View File
@@ -15,56 +15,6 @@
This chapter describes each development method. This chapter describes each development method.
</para> </para>
<section id="platdev-appdev-external-sdk">
<title>External Development Using the Meta-Toolchain</title>
<para>
The Yocto Project provides toolchains that allow you to develop your application
outside of the Yocto Project build system for specific hardware.
These toolchains (called meta-toolchains) contain cross-development tools such as compilers,
linkers, and debuggers that build your application for your target device.
The Yocto Project also provides images that have toolchains for supported
architectures included within the image.
This allows you to compile, debug, or profile applications directly on the target device.
See the
"<link linkend='ref-images'>Reference: Images</link>" appendix for a listing of the image
types that Yocto Project supports.
</para>
<para>
Using the BitBake tool you can build a meta-toolchain or meta-toolchain-sdk target,
which generates a tarball.
Unpacking this tarball into the <filename class="directory">/opt/poky</filename> directory
on your host produces a setup script
(e.g. <filename>/opt/poky/environment-setup-i586-poky-linux</filename>) that
you can <filename>source</filename> to initialize your build environment.
Sourcing this script adds the compiler, QEMU scripts, QEMU binary, a special version of
<filename>pkgconfig</filename> and other
useful utilities to the <filename>PATH</filename> variable used by the Yocto Project
build environment.
Variables to assist <filename>pkgconfig</filename> and
Autotools are also defined so that, for example, <filename>configure</filename>
can find pre-generated test results for tests that need target hardware on which to run.
</para>
<para>
Using the toolchain with Autotool-enabled packages is straightforward - just pass the
appropriate <filename>host</filename> option to <filename>configure</filename>.
Following is an example:
<literallayout class='monospaced'>
$ ./configure --host=arm-poky-linux-gnueabi
</literallayout>
For projects that are not Autotool-enabled, it is usually just a case of ensuring
you point to and use the cross-toolchain.
For example, the following two lines of code in a <filename>Makefile</filename>
that builds your application
specify to use the cross-compiler <filename>arm-poky-linux-gnueabi-gcc</filename>
and linker <filename>arm-poky-linux-gnueabi-ld</filename>, which are part of the
meta-toolchain you would have previously established:
<literallayout class='monospaced'>
CC=arm-poky-linux-gnueabi-gcc;
LD=arm-poky-linux-gnueabi-ld;
</literallayout>
</para>
</section>
<section id="using-the-eclipse-and-anjuta-plug-ins"> <section id="using-the-eclipse-and-anjuta-plug-ins">
<title>External Development Using the Eclipse Plug-in</title> <title>External Development Using the Eclipse Plug-in</title>
<para> <para>