summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2014-11-21 06:40:49 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-12-09 15:09:06 +0000
commit117c9b4a64a4c490b353e31567d0a593bac98a3f (patch)
treeabdb3015a770e93d6d85b1a5f98ff0d7761cca76
parent81fb49bb05a24e0c61ecb918443d6fa18acead64 (diff)
downloadpoky-117c9b4a64a4c490b353e31567d0a593bac98a3f.tar.gz
dev-manual: Edits to the multi-machine builds section.
Fixes [YOCTO #5400] I applied some review edits to this section as suggested by Richard Purdie. (From yocto-docs rev: a1898cf65537e732e0e42605bb28d636077e7f56) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml24
1 files changed, 12 insertions, 12 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index a710efe6d5..664b2943c3 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -5988,10 +5988,10 @@ Gateways via their Web Interfaces</ulink>"</emphasis>
5988 CPU core used in a system might enable some micro optimizations 5988 CPU core used in a system might enable some micro optimizations
5989 in GCC for that particular system but would otherwise not gain 5989 in GCC for that particular system but would otherwise not gain
5990 you much of a performance difference across the other systems 5990 you much of a performance difference across the other systems
5991 as compared to using a more general tuning across all the builds. 5991 as compared to using a more general tuning across all the builds
5992 Another example is setting 5992 (e.g. setting
5993 <ulink url='var-DEFAULTTUNE'><filename>DEFAULTTUNE</filename></ulink> 5993 <ulink url='var-DEFAULTTUNE'><filename>DEFAULTTUNE</filename></ulink>
5994 specifically for each machine's build. 5994 specifically for each machine's build).
5995 Rather than "max out" each build's tunings, you can take steps that 5995 Rather than "max out" each build's tunings, you can take steps that
5996 cause the OpenEmbedded build system to reuse software across the 5996 cause the OpenEmbedded build system to reuse software across the
5997 various machines where it makes sense. 5997 various machines where it makes sense.
@@ -6044,7 +6044,7 @@ Gateways via their Web Interfaces</ulink>"</emphasis>
6044 <ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-allarch'><filename>allarch</filename></ulink> 6044 <ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-allarch'><filename>allarch</filename></ulink>
6045 class. 6045 class.
6046 This class is useful for "all" architectures because it 6046 This class is useful for "all" architectures because it
6047 contains many other variables that can be used across 6047 configures many variables so packages can be used across
6048 multiple architectures.</para> 6048 multiple architectures.</para>
6049 <para>If your recipe needs to generate packages that are 6049 <para>If your recipe needs to generate packages that are
6050 machine-specific or when one of the build or runtime 6050 machine-specific or when one of the build or runtime
@@ -6057,17 +6057,14 @@ Gateways via their Web Interfaces</ulink>"</emphasis>
6057 <literallayout class='monospaced'> 6057 <literallayout class='monospaced'>
6058 PACKAGE_ARCH = "${MACHINE_ARCH}" 6058 PACKAGE_ARCH = "${MACHINE_ARCH}"
6059 </literallayout> 6059 </literallayout>
6060 If you select a specific tuning for the recipe, 6060 When you do not specifically enable a package
6061 the OpenEmbedded build system enables the package
6062 architecture defined by that tuning file.</para>
6063 <para>When you do not specifically enable a package
6064 architecture through the 6061 architecture through the
6065 <ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_ARCH'><filename>PACKAGE_ARCH</filename></ulink>, 6062 <ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_ARCH'><filename>PACKAGE_ARCH</filename></ulink>,
6066 The OpenEmbedded build system defaults to the 6063 The OpenEmbedded build system defaults to the
6067 <ulink url='&YOCTO_DOCS_REF_URL;#var-TUNE_ARCH'><filename>TUNE_ARCH</filename></ulink> 6064 <ulink url='&YOCTO_DOCS_REF_URL;#var-TUNE_ARCH'><filename>TUNE_ARCH</filename></ulink>
6068 setting: 6065 setting:
6069 <literallayout class='monospaced'> 6066 <literallayout class='monospaced'>
6070 PACKAGE_ARCH == TUNE_ARCH 6067 PACKAGE_ARCH = "${TUNE_ARCH}"
6071 </literallayout> 6068 </literallayout>
6072 </para></listitem> 6069 </para></listitem>
6073 <listitem><para><emphasis>Choose a Generic Tuning File if Possible:</emphasis> 6070 <listitem><para><emphasis>Choose a Generic Tuning File if Possible:</emphasis>
@@ -6076,7 +6073,9 @@ Gateways via their Web Interfaces</ulink>"</emphasis>
6076 run on <filename>armv6</filename> and 6073 run on <filename>armv6</filename> and
6077 <filename>armv7</filename> processors in most cases). 6074 <filename>armv7</filename> processors in most cases).
6078 Similarly, <filename>i486</filename> binaries could work 6075 Similarly, <filename>i486</filename> binaries could work
6079 on <filename>i586</filename> and higher processors.</para> 6076 on <filename>i586</filename> and higher processors.
6077 You should realize, however, that advances on newer
6078 processor versions would not be used.</para>
6080 <para>If you select the same tune for several different 6079 <para>If you select the same tune for several different
6081 machines, the OpenEmbedded build system reuses software 6080 machines, the OpenEmbedded build system reuses software
6082 previously built, thus speeding up the overall build time. 6081 previously built, thus speeding up the overall build time.
@@ -6085,7 +6084,7 @@ Gateways via their Web Interfaces</ulink>"</emphasis>
6085 package feed exists. 6084 package feed exists.
6086 </para></listitem> 6085 </para></listitem>
6087 <listitem><para><emphasis>Manage Granular Level Packaging:</emphasis> 6086 <listitem><para><emphasis>Manage Granular Level Packaging:</emphasis>
6088 Sometimes cases exist where where injecting another level 6087 Sometimes cases exist where injecting another level
6089 of package architecture beyond the three higher levels 6088 of package architecture beyond the three higher levels
6090 noted earlier can be useful. 6089 noted earlier can be useful.
6091 For example, consider the <filename>emgd</filename> 6090 For example, consider the <filename>emgd</filename>
@@ -6096,7 +6095,8 @@ Gateways via their Web Interfaces</ulink>"</emphasis>
6096 generic packages. 6095 generic packages.
6097 You can examine the key code in the 6096 You can examine the key code in the
6098 <ulink url='http://git.yoctoproject.org/cgit/cgit.cgi'>Source Repositories</ulink> 6097 <ulink url='http://git.yoctoproject.org/cgit/cgit.cgi'>Source Repositories</ulink>
6099 in <filename>classes/emgd-gl.bbclass</filename>. 6098 "daisy" branch in
6099 <filename>classes/emgd-gl.bbclass</filename>.
6100 For a specific set of packages, the code redefines 6100 For a specific set of packages, the code redefines
6101 <ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_ARCH'><filename>PACKAGE_ARCH</filename></ulink>. 6101 <ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_ARCH'><filename>PACKAGE_ARCH</filename></ulink>.
6102 <ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_EXTRA_ARCHS'><filename>PACKAGE_EXTRA_ARCHS</filename></ulink> 6102 <ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_EXTRA_ARCHS'><filename>PACKAGE_EXTRA_ARCHS</filename></ulink>