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

ref-manual: Applied minor corrections to 2.2 migration section. 

Moved a couple notes around and changed some wordings...
nothing major.

(From yocto-docs rev: 75be6c30ca646ee81b955fae7a3e0183ead9ca08)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2016-10-21 13:33:47 -07:00 committed by Richard Purdie
parent d89a35f0a0
commit e0ed9253c1
1 changed files with 7 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
documentation/ref-manual/migration.xml
View File

@ -3392,10 +3392,6 @@
<para> <para>
The following changes for Python occurred: The following changes for Python occurred:
<note>
Python 2 and recipes that use it can still be built for the
target as with previous versions.
</note>
</para> </para>
<section id='migration-2.2-bitbake-now-requires-python-3.4'> <section id='migration-2.2-bitbake-now-requires-python-3.4'>
@ -3443,6 +3439,10 @@
Unfortunately, systems using RPM as a package manager and Unfortunately, systems using RPM as a package manager and
providing online package-manager support through SMART still providing online package-manager support through SMART still
require Python 2. require Python 2.
<note>
Python 2 and recipes that use it can still be built for the
target as with previous versions.
</note>
</para> </para>
</section> </section>
@ -3489,6 +3489,7 @@
<para> <para>
<filename>runqemu</filename> has been ported to Python and has <filename>runqemu</filename> has been ported to Python and has
changed behavior in some cases. changed behavior in some cases.
Previous usage patterns continued to be supported.
</para> </para>
<para> <para>
@ -3508,9 +3509,6 @@
Using a configuration file is particularly convenient when trying Using a configuration file is particularly convenient when trying
to use QEMU with machines other than the to use QEMU with machines other than the
<filename>qemu*</filename> machines in OE-Core. <filename>qemu*</filename> machines in OE-Core.
<note>
Previous usage patterns are continued to be supported.
</note>
The <filename>qemuboot.conf</filename> file is generated by the The <filename>qemuboot.conf</filename> file is generated by the
<filename>qemuboot</filename> <filename>qemuboot</filename>
class when the root filesystem is being build (i.e. class when the root filesystem is being build (i.e.
@ -3612,8 +3610,8 @@ $ runqemu qemux86-64 tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.
binary" QA issues when building such recipes. binary" QA issues when building such recipes.
You need to fix these recipes so that they use the expected You need to fix these recipes so that they use the expected
<filename>LDFLAGS</filename>. <filename>LDFLAGS</filename>.
Depending on how the software is built, the build system might Depending on how the software is built, the build system used by
need to be patched. the software (e.g. a Makefile) might need to be patched.
However, sometimes making this fix is as simple as adding the However, sometimes making this fix is as simple as adding the
following to the recipe: following to the recipe:
<literallayout class='monospaced'> <literallayout class='monospaced'>