ref-manual: Updated the allarch class description.
Added a patch to include a note from Andre. Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
a8674ae642
commit
7d30d67b26
|
@ -52,20 +52,22 @@
|
||||||
and a C library as pre-requisites, and splitting out of debug symbols
|
and a C library as pre-requisites, and splitting out of debug symbols
|
||||||
during packaging).
|
during packaging).
|
||||||
<note>
|
<note>
|
||||||
Unlike e.g. Debian, OpenEmbedded recipes that produce packages
|
<para>Unlike some distro recipes (e.g. Debian), OpenEmbedded recipes
|
||||||
which
|
that produce packages that depend on tunings through use of the
|
||||||
<link linkend='var-RDEPENDS'><filename>RDEPENDS</filename></link>
|
<link linkend='var-RDEPENDS'><filename>RDEPENDS</filename></link>
|
||||||
on
|
and
|
||||||
<link linkend='var-TUNE_PKGARCH'><filename>TUNE_PKGARCH</filename></link>
|
<link linkend='var-TUNE_PKGARCH'><filename>TUNE_PKGARCH</filename></link>
|
||||||
packages should never be made <filename>allarch</filename>, even
|
variables, should never be configured for all architectures
|
||||||
if they do not produce architecture-specific output. This would
|
using <filename>allarch</filename>.
|
||||||
cause the do_package_write_* tasks to have different signatures
|
This is the case even if the recipes do not produce
|
||||||
for
|
architecture-specific output.</para>
|
||||||
<link linkend='var-MACHINE'><filename>MACHINE</filename></link>s
|
<para>Configuring such recipes for all architectures causes the
|
||||||
with different
|
<link linkend='ref-tasks-package_write_deb'><filename>do_package_write_*</filename></link>
|
||||||
<link linkend='var-TUNE_PKGARCH'><filename>TUNE_PKGARCH</filename></link>,
|
tasks to have different signatures for the machines with different
|
||||||
thus unnecessary rebuilds every single time an image for a different
|
tunings.
|
||||||
MACHINE is built (even without any change to the recipe).
|
Additionally, unnecessary rebuilds occur every time an
|
||||||
|
image for a different <filename>MACHINE</filename> is built
|
||||||
|
even when the recipe never changes.</para>
|
||||||
</note>
|
</note>
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue