dev-manual: use actual machine override demonstration

Given that the section in question is describing how to configure
dependencies based on the machine type, it seems inappropriate to use
an example that depends on the choice of C library, so grab a snippet
from linux-yocto.inc to really drive the point home.

(From yocto-docs rev: 66bfec015f61a690f96cf8e28b80869c77327e6d)

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
rpjday@crashcourse.ca
2020-03-28 16:35:00 -04:00
committed by Richard Purdie
parent 0bcf88c375
commit 5f6e055dc8

View File

@@ -319,12 +319,26 @@
DEPENDS_append_one = " foo" DEPENDS_append_one = " foo"
DEPENDS_prepend_one = "foo " DEPENDS_prepend_one = "foo "
</literallayout> </literallayout>
As an actual example, here's a line from the recipe As an actual example, here's a snippet from the
for gnutls, which adds dependencies on generic kernel include file
"argp-standalone" when building with the musl C <filename>linux-yocto.inc</filename>,
library: wherein the kernel compile and link options are
adjusted in the case of a subset of the supported
architectures:
<literallayout class='monospaced'> <literallayout class='monospaced'>
DEPENDS_append_libc-musl = " argp-standalone" DEPENDS_append_aarch64 = " libgcc"
KERNEL_CC_append_aarch64 = " ${TOOLCHAIN_OPTIONS}"
KERNEL_LD_append_aarch64 = " ${TOOLCHAIN_OPTIONS}"
DEPENDS_append_nios2 = " libgcc"
KERNEL_CC_append_nios2 = " ${TOOLCHAIN_OPTIONS}"
KERNEL_LD_append_nios2 = " ${TOOLCHAIN_OPTIONS}"
DEPENDS_append_arc = " libgcc"
KERNEL_CC_append_arc = " ${TOOLCHAIN_OPTIONS}"
KERNEL_LD_append_arc = " ${TOOLCHAIN_OPTIONS}"
KERNEL_FEATURES_append_qemuall=" features/debug/printk.scc"
</literallayout> </literallayout>
<note> <note>
Avoiding "+=" and "=+" and using Avoiding "+=" and "=+" and using