From de42e04de72a4ab081cd0e0b3e8a0c2ed00ad66d Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 2 Dec 2013 15:47:00 -0600 Subject: [PATCH] ref-manual: Edits to image_types class. Noticed that this class file name is "image_types.bbclass" and not "image-types.bbclass". Fixed it. (From yocto-docs rev: 354aa820a13f2dcff32e8a24cbce477c3d6b54f6) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-classes.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml index d65ac0b0bd..2cc962eead 100644 --- a/documentation/ref-manual/ref-classes.xml +++ b/documentation/ref-manual/ref-classes.xml @@ -940,11 +940,11 @@ -
- <filename>image-types.bbclass</filename> +
+ <filename>image_types.bbclass</filename> - The image types (image-types) class defines all of + The image types (image_types) class defines all of the standard image output types that you can enable through the IMAGE_FSTYPES variable. @@ -959,8 +959,8 @@ image.bbclass. If you define your own image types using a custom BitBake class and then use IMAGE_CLASSES to enable it, the custom - class must either inherit image-types or - image-types must also appear in + class must either inherit image_types or + image_types must also appear in IMAGE_CLASSES.