|author||Patrick Williams <firstname.lastname@example.org>||2016-06-22 11:31:46 -0500|
|committer||Richard Purdie <email@example.com>||2016-07-01 16:22:45 +0100|
linux-libc-headers: Update doc for recipe depends
The previous documentation has not been accurate since at least commit 6a1ff0e. Recipes that follow the old documentation will not correctly build when sstate is enabled because the kernel source will not actually be available. (From OE-Core rev: 8e7522aae65b3ab0a2ded257d5c82e030fe2d710) Signed-off-by: Patrick Williams <firstname.lastname@example.org> Signed-off-by: Ross Burton <email@example.com> Signed-off-by: Richard Purdie <firstname.lastname@example.org>
1 files changed, 4 insertions, 3 deletions
diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc
index 2ba6ed51df..92acf8aa0b 100644
@@ -18,9 +18,10 @@ LICENSE = "GPLv2"
# But you have some kernel headers you need for some driver? That is fine
# but get them from STAGING_KERNEL_DIR where the kernel installs itself.
# This will make the package using them machine specific but this is much
-# better than having a machine specific C library. This does mean your
-# recipe needs a DEPENDS += "virtual/kernel" but again, that is fine and
-# makes total sense.
+# better than having a machine specific C library. This does mean your
+# recipe needs a
+# do_configure[depends] += "virtual/kernel:do_shared_workdir"
+# but again, that is fine and makes total sense.
# There can also be a case where your kernel extremely old and you want
# an older libc ABI for that old kernel. The headers installed by this