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

ref-manual: Updated the 2.2 Migration section with review changes. 

(From yocto-docs rev: 4af78f942bedb55e46280bc0fc878f174e15b479)

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-14 08:23:11 -07:00 committed by Richard Purdie
parent d669b83797
commit f9ea0a8770
1 changed files with 120 additions and 56 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -3345,7 +3345,8 @@
<title>Minimum Kernel Version</title> <title>Minimum Kernel Version</title>
<para> <para>
The minimum kernel version is now 3.2.0, due to the upgrade The minimum kernel version for the target system and for SDK
is now 3.2.0, due to the upgrade
to <filename>glibc 2.24</filename>. to <filename>glibc 2.24</filename>.
Specifically, for AArch64-based targets the version is Specifically, for AArch64-based targets the version is
3.14. 3.14.
@ -3387,51 +3388,81 @@
</para> </para>
</section> </section>
<section id='migration-2.2-bitbake-now-requires-python-3.4'> <section id='migration-2.2-python-changes'>
<title>BitBake Now Requires Python 3.4+</title> <title>Python Changes</title>
<para> <para>
BitBake requires Python 3.4 or greater. 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>
<section id='migration-2.2-metadata-now-must-use-python-3-syntax'> <section id='migration-2.2-bitbake-now-requires-python-3.4'>
<title>Metadata Must Now Use Python 3 Syntax</title> <title>BitBake Now Requires Python 3.4+</title>
<para> <para>
The metadata is now required to use Python 3 syntax. BitBake requires Python 3.4 or greater.
For help preparing metadata, see any of the many Python 3 porting </para>
guides available. </section>
Alternatively, you can reference the conversion commits for Bitbake
and you can use OE-Core as a guide for changes. <section id='migration-2.2-utf-8-locale-required-on-build-host'>
Following are particular areas of interest: <title>UTF-8 Locale Required on Build Host</title>
<literallayout class='monospaced'>
<para>
A UTF-8 locale is required on the build host due to Python 3.
Since C.UTF-8 is not a standard, the default is en_US.UTF-8.
</para>
</section>
<section id='migration-2.2-metadata-now-must-use-python-3-syntax'>
<title>Metadata Must Now Use Python 3 Syntax</title>
<para>
The metadata is now required to use Python 3 syntax.
For help preparing metadata, see any of the many Python 3 porting
guides available.
Alternatively, you can reference the conversion commits for Bitbake
and you can use OE-Core as a guide for changes.
Following are particular areas of interest:
<literallayout class='monospaced'>
* subprocess command-line pipes needing locale decoding * subprocess command-line pipes needing locale decoding
* the syntax for octal values changed * the syntax for octal values changed
* the <filename>iter*()</filename> functions changed name * the <filename>iter*()</filename> functions changed name
* iterators now return views * iterators now return views, not lists
* not lists
* changed names for Python modules * changed names for Python modules
</literallayout> </literallayout>
</para> </para>
</section> </section>
<section id='migration-2.2-target-python-recipes-switched-to-python-3'> <section id='migration-2.2-target-python-recipes-switched-to-python-3'>
<title>Target Python Recipes Switched to Python 3</title> <title>Target Python Recipes Switched to Python 3</title>
<para> <para>
Most target Python recipes have now been switched to Python 3. Most target Python recipes have now been switched to Python 3.
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.
</para> </para>
</section>
<section id='migration-2.2-buildtools-tarball-includes-python-3'>
<title><filename>buildtools-tarball</filename> Includes Python 3</title>
<para>
<filename>buildtools-tarball</filename> now includes Python 3.
</para>
</section>
</section> </section>
<section id='migration-2.2-uclibc-replaced-by-musl'> <section id='migration-2.2-uclibc-replaced-by-musl'>
<title>uClibc Replaced by musl</title> <title>uClibc Replaced by musl</title>
<para> <para>
Uclibc has been removed in favor of musl. uClibc has been removed in favor of musl.
Musl has matured, is better maintained, and is compatible with a
wider range of applications as compared to uClibc.
</para> </para>
</section> </section>
@ -3453,15 +3484,6 @@
</para> </para>
</section> </section>
<section id='migration-2.2-utf-8-locale-required-on-build-host'>
<title>UTF-8 Locale Required on Build Host</title>
<para>
A UTF-8 locale is required on the build host due to Python 3.
Since C.UTF-8 is not a standard, the default is en_US.UTF-8.
</para>
</section>
<section id='migration-2.2-runqemu-ported-to-python'> <section id='migration-2.2-runqemu-ported-to-python'>
<title><filename>runqemu</filename> Ported to Python</title> <title><filename>runqemu</filename> Ported to Python</title>
@ -3471,6 +3493,28 @@
</para> </para>
</section> </section>
<section id='migration-2.2-default-linker-hash-style-changed'>
<title>Default Linker Hash Style Changed</title>
<para>
The default linker hash style for <filename>gcc-cross</filename>
is now "sysv" in order to catch recipes that are building software
without using the OpenEmbedded
<link linkend='var-LDFLAGS'><filename>LDFLAGS</filename></link>.
This change could result in seeing some "No GNU_HASH in the elf
binary" QA issues when building such recipes.
You need to fix these recipes so that they use the expected
<filename>LDFLAGS</filename>.
Depending on how the software is built, the build system might
need to be patched.
However, sometimes making this fix is as simple as adding the
following to the recipe:
<literallayout class='monospaced'>
TARGET_CC_ARCH += "${LDFLAGS}"
</literallayout>
</para>
</section>
<section id='migration-2.2-bitbake-changes'> <section id='migration-2.2-bitbake-changes'>
<title>BitBake Changes</title> <title>BitBake Changes</title>
@ -3499,8 +3543,8 @@
<filename>SRC_URI</filename>. <filename>SRC_URI</filename>.
</para></listitem> </para></listitem>
<listitem><para> <listitem><para>
Some of BitBake's internal code structures for storing the Some of BitBake's internal code structures for accessing
recipe cache needed to be changed to support the new the recipe cache needed to be changed to support the new
multi-configuration functionality. multi-configuration functionality.
These changes will affect external tools that use BitBake's These changes will affect external tools that use BitBake's
tinfoil module. tinfoil module.
@ -3715,7 +3759,8 @@
</para></listitem> </para></listitem>
<listitem><para> <listitem><para>
<filename>util-linux</filename>: <filename>util-linux</filename>:
Make <filename>prlimit</filename> a separate package. Moved <filename>prlimit</filename> to a separate
<filename>util-linux-prlimit</filename> package.
</para></listitem> </para></listitem>
</itemizedlist> </itemizedlist>
</para> </para>
@ -3727,26 +3772,22 @@
<para> <para>
The following miscellaneous changes have occurred: The following miscellaneous changes have occurred:
<itemizedlist> <itemizedlist>
<listitem><para>
<filename>buildtools-tarball</filename>:
Replaced <filename>nativesdk-python</filename>
with <filename>nativesdk-python3</filename>.
</para></listitem>
<listitem><para> <listitem><para>
<filename>package_regex.inc</filename>: <filename>package_regex.inc</filename>:
Removed deprecated file. Removed because the definitions
<filename>package_regex.inc</filename> previously contained
have been moved to their respective recipes.
</para></listitem> </para></listitem>
<listitem><para> <listitem><para>
<filename>recipetool</filename>: Both <filename>devtool add</filename> and
Set a fixed <filename>recipetool create</filename> now use a fixed
<link linkend='var-SRCREV'><filename>SRCREV</filename></link> <link linkend='var-SRCREV'><filename>SRCREV</filename></link>
by default when fetching from Git. by default when fetching from a Git repository.
</para></listitem> You can override this in either case to use
<listitem><para> <filename>${</filename><link linkend='var-AUTOREV'><filename>AUTOREV</filename></link><filename>}</filename>
<filename>devtool</filename>: instead by using the <filename>-a</filename> or
Set a fixed <filename>&dash;&dash;autorev</filename> command-line
<link linkend='var-SRCREV'><filename>SRCREV</filename></link> option
by default when fetching from Git.
</para></listitem> </para></listitem>
<listitem><para> <listitem><para>
<filename>distcc</filename>: <filename>distcc</filename>:
@ -3759,6 +3800,29 @@
<listitem><para> <listitem><para>
<filename>image.bbclass</filename>: <filename>image.bbclass</filename>:
Renamed COMPRESS(ION) to CONVERSION. Renamed COMPRESS(ION) to CONVERSION.
This change means that
<filename>COMPRESSIONTYPES</filename>,
<filename>COMPRESS_DEPENDS</filename> and
<filename>COMPRESS_CMD</filename> are deprecated in favor
of <filename>CONVERSIONTYPES</filename>,
<filename>CONVERSION_DEPENDS</filename> and
<filename>CONVERSION_CMD</filename>.
The <filename>COMPRESS*</filename> variable names will
still work in the 2.2 release but metadata that does not
need to be backwards-compatible should be changed to
use the new names as the <filename>COMPRESS*</filename>
ones will be removed in a future release.
</para></listitem>
<listitem><para>
<filename>gtk-doc</filename>:
A full version of <filename>gtk-doc</filename> is now
made available.
However, some old software might not be capable of using
the current version of <filename>gtk-doc</filename>
to build documentation.
You need to change recipes that build such software so that
they explicitly disable building documentation with
<filename>gtk-doc</filename>.
</para></listitem> </para></listitem>
</itemizedlist> </itemizedlist>
</para> </para>