From a6820f43f597fed57eb1f3eacb963ddf5bd0f1f0 Mon Sep 17 00:00:00 2001 From: Robert Cochran Date: Mon, 16 Apr 2012 07:50:57 -0600 Subject: documentation/dev-manual/dev-manual-common-tasks.xml: Fixed example 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. (From yocto-docs rev: 977877efa7781dd00c53cfa914dd710de7d934a1) Signed-off-by: Robert Cochran Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-common-tasks.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'documentation') diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index a32085d678..a81b6562ec 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 - meta/recipes-sato/tasks/task-poky.bb. + meta/recipes-core/tasks/task-core-boot.bb The PACKAGES variable lists the task packages to build along with the complementary -- cgit v1.2.3-54-g00ecf