sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

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 <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2013-12-02 15:47:00 -06:00 committed by Richard Purdie
parent 5f24d24595
commit de42e04de7
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
documentation/ref-manual/ref-classes.xml
View File

@ -940,11 +940,11 @@
</para>
</section>
<section id='ref-classes-image-types'>
<title><filename>image-types.bbclass</filename></title>
<section id='ref-classes-image_types'>
<title><filename>image_types.bbclass</filename></title>
<para>
The image types (<filename>image-types</filename>) class defines all of
The image types (<filename>image_types</filename>) class defines all of
the standard image output types that you can enable through the
<link linkend='var-IMAGE_FSTYPES'><filename>IMAGE_FSTYPES</filename></link>
variable.
@ -959,8 +959,8 @@
<link linkend='ref-classes-image'><filename>image.bbclass</filename></link>.
If you define your own image types using a custom BitBake class and
then use <filename>IMAGE_CLASSES</filename> to enable it, the custom
class must either inherit <filename>image-types</filename> or
<filename>image-types</filename> must also appear in
class must either inherit <filename>image_types</filename> or
<filename>image_types</filename> must also appear in
<filename>IMAGE_CLASSES</filename>.
</para>
</section>