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

documentation/dev-manual/dev-manual-kernel-appendix.xml: cleared up note 

There is note instructing the user to delete unused .bbappend files
or comment out the COMPATIBLE_MACHINE statements in those unused
files before running the build in the example.  the note was not
clear about the COMPATIBLE_MACHINE statement in the .bbappend file
that is actually being used.  I edited the text to be clear about
that.

(From yocto-docs rev: 44277b9c5d8a77958a4220fa790bc13e9ce697b3)

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 2012-01-12 12:26:22 -06:00 committed by Richard Purdie
parent 405578286d
commit b9232eb2b4
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
documentation/dev-manual/dev-manual-kernel-appendix.xml
View File

@ -438,7 +438,8 @@
Because all the kernel <filename>.bbappend</filename> files are parsed during the Because all the kernel <filename>.bbappend</filename> files are parsed during the
build process regardless of whether you are using them or not, you should either build process regardless of whether you are using them or not, you should either
comment out the <filename>COMPATIBLE_MACHINE</filename> statements in all comment out the <filename>COMPATIBLE_MACHINE</filename> statements in all
<filename>.bbappend</filename> files, or you should simply remove all the files unused <filename>.bbappend</filename> files.
Alternatively, you can simply remove all the files
except the one your are using for the build except the one your are using for the build
(i.e. <filename>linux-yocto_3.0.bbappend</filename> in this example). (i.e. <filename>linux-yocto_3.0.bbappend</filename> in this example).
</note> </note>