A reference to meta/recipes-sato/tasks/task-poky.bb is made as a good
example of a task; however, this file / recipe doesn't exist. I
replaced it with meta/recipes-core/tasks/task-core-boot.bb, which I
think is a both useful and basic example to consider.
Signed-off-by: Robert Cochran<[email protected]>
---
.../dev-manual/dev-manual-common-tasks.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml
b/documentation/dev-manual/dev-manual-common-tasks.xml
index a32085d..a81b656 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -495,7 +495,7 @@
For complex custom images, the best approach is to
create a custom task package
that is used to build the image or images.
A good example of a tasks package is
- <filename>meta/recipes-sato/tasks/task-poky.bb</filename>.
+
<filename>meta/recipes-core/tasks/task-core-boot.bb</filename>
The
<filename><ulink
url='&YOCTO_DOCS_REF_URL;#var-PACKAGES'>PACKAGES</ulink></filename>
variable lists the task packages to build along with
the complementary
--
1.7.5.4
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
