summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual/adt-prepare.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-11-14 11:36:19 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-12-03 13:52:55 +0000
commit55530d42e70ec1ceb8e68cbd4165fd96c358a29e (patch)
tree5499a4dcbe1669b2388d639b9153bfee2511a7cb /documentation/adt-manual/adt-prepare.xml
parente197fca49c2ccb95ac6ec0868d4f0af877592e89 (diff)
downloadpoky-55530d42e70ec1ceb8e68cbd4165fd96c358a29e.tar.gz
documentation: adt-manual - autotools-based projects
Fixes [YOCTO #2645] In the section that describes how to build a toolchain using bitbake meta-toolchain, I updated the note about the MACHINE and SDKMACHINE variables. These needed to be pointed out to the user as important variables for correct settings before generating the toolchain. I added a new section for the autotools-based programs that now includes a simple "Hello World" example. This section precedes the section that describes how to pass host options to configure.sh. (From yocto-docs rev: 9849e7b94d42a851f30f0fba8ae60916697956dd) 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.xml16
1 files changed, 12 insertions, 4 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 3fd231c6a0..040618482f 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -18,7 +18,7 @@
18 18
19 <para> 19 <para>
20 The following list describes installation methods that set up varying degrees of tool 20 The following list describes installation methods that set up varying degrees of tool
21 availabiltiy on your system. 21 availability on your system.
22 Regardless of the installation method you choose, 22 Regardless of the installation method you choose,
23 you must <filename>source</filename> the cross-toolchain 23 you must <filename>source</filename> the cross-toolchain
24 environment setup script before you use a toolchain. 24 environment setup script before you use a toolchain.
@@ -258,9 +258,17 @@
258 <filename>bitbake meta-toolchain</filename>.</para> 258 <filename>bitbake meta-toolchain</filename>.</para>
259 <para>Use the appropriate <filename>bitbake</filename> command only after you have 259 <para>Use the appropriate <filename>bitbake</filename> command only after you have
260 sourced the <filename>&OE_INIT_PATH;</filename> script located in the Source 260 sourced the <filename>&OE_INIT_PATH;</filename> script located in the Source
261 Directory. 261 Directory and you have made sure your <filename>conf/local.conf</filename>
262 When the <filename>bitbake</filename> command completes, the toolchain installer will 262 variables are correct.
263 be in <filename>tmp/deploy/sdk</filename> in the Build Directory. 263 In particular, you need to be sure the
264 <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
265 variable matches the architecture for which you are building and that the
266 <filename>SDKMACHINE</filename> variable is correctly set if you are building
267 a toolchain for an architecture that differs from your current
268 development host machine.</para>
269 <para>When the <filename>bitbake</filename> command completes, the
270 toolchain installer will be in <filename>tmp/deploy/sdk</filename> in the
271 Build Directory.
264 </para></note> 272 </para></note>
265 </para></listitem> 273 </para></listitem>
266 <listitem><para>Once you have the installer, run it to install the toolchain. 274 <listitem><para>Once you have the installer, run it to install the toolchain.