From f9ea0a877095a59d50e9ebedf940e6cbba5c7c35 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 14 Oct 2016 08:23:11 -0700 Subject: ref-manual: Updated the 2.2 Migration section with review changes. (From yocto-docs rev: 4af78f942bedb55e46280bc0fc878f174e15b479) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/migration.xml | 174 ++++++++++++++++++++++----------- 1 file changed, 119 insertions(+), 55 deletions(-) (limited to 'documentation') diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml index 4ac36e5cf8..4cf72612bf 100644 --- a/documentation/ref-manual/migration.xml +++ b/documentation/ref-manual/migration.xml @@ -3345,7 +3345,8 @@ Minimum Kernel Version - 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 glibc 2.24. Specifically, for AArch64-based targets the version is 3.14. @@ -3387,51 +3388,81 @@ -
- BitBake Now Requires Python 3.4+ +
+ Python Changes - BitBake requires Python 3.4 or greater. + The following changes for Python occurred: + + Python 2 and recipes that use it can still be built for the + target as with previous versions. + -
-
- Metadata Must Now Use Python 3 Syntax +
+ BitBake Now Requires Python 3.4+ - - 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: - + + BitBake requires Python 3.4 or greater. + +
+ +
+ UTF-8 Locale Required on Build Host + + + 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. + +
+ +
+ Metadata Must Now Use Python 3 Syntax + + + 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: + * subprocess command-line pipes needing locale decoding * the syntax for octal values changed * the iter*() functions changed name - * iterators now return views - * not lists + * iterators now return views, not lists * changed names for Python modules - - -
+ + +
-
- Target Python Recipes Switched to Python 3 +
+ Target Python Recipes Switched to Python 3 - - Most target Python recipes have now been switched to Python 3. - Unfortunately, systems using RPM as a package manager and - providing online package-manager support through SMART still - require Python 2. - + + Most target Python recipes have now been switched to Python 3. + Unfortunately, systems using RPM as a package manager and + providing online package-manager support through SMART still + require Python 2. + +
+ +
+ <filename>buildtools-tarball</filename> Includes Python 3 + + + buildtools-tarball now includes Python 3. + +
uClibc Replaced by musl - 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.
@@ -3453,21 +3484,34 @@
-
- UTF-8 Locale Required on Build Host +
+ <filename>runqemu</filename> Ported to Python - 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. + runqemu has been ported to Python and has + changed behavior in some cases.
-
- <filename>runqemu</filename> Ported to Python +
+ Default Linker Hash Style Changed - runqemu has been ported to Python and has - changed behavior in some cases. + The default linker hash style for gcc-cross + is now "sysv" in order to catch recipes that are building software + without using the OpenEmbedded + LDFLAGS. + 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 + LDFLAGS. + 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: + + TARGET_CC_ARCH += "${LDFLAGS}" +
@@ -3499,8 +3543,8 @@ SRC_URI. - Some of BitBake's internal code structures for storing the - recipe cache needed to be changed to support the new + Some of BitBake's internal code structures for accessing + the recipe cache needed to be changed to support the new multi-configuration functionality. These changes will affect external tools that use BitBake's tinfoil module. @@ -3715,7 +3759,8 @@ util-linux: - Make prlimit a separate package. + Moved prlimit to a separate + util-linux-prlimit package. @@ -3727,26 +3772,22 @@ The following miscellaneous changes have occurred: - - buildtools-tarball: - Replaced nativesdk-python - with nativesdk-python3. - package_regex.inc: - Removed deprecated file. - - - recipetool: - Set a fixed - SRCREV - by default when fetching from Git. + Removed because the definitions + package_regex.inc previously contained + have been moved to their respective recipes. - devtool: - Set a fixed + Both devtool add and + recipetool create now use a fixed SRCREV - by default when fetching from Git. + by default when fetching from a Git repository. + You can override this in either case to use + ${AUTOREV} + instead by using the -a or + ‐‐autorev command-line + option distcc: @@ -3759,6 +3800,29 @@ image.bbclass: Renamed COMPRESS(ION) to CONVERSION. + This change means that + COMPRESSIONTYPES, + COMPRESS_DEPENDS and + COMPRESS_CMD are deprecated in favor + of CONVERSIONTYPES, + CONVERSION_DEPENDS and + CONVERSION_CMD. + The COMPRESS* 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 COMPRESS* + ones will be removed in a future release. + + + gtk-doc: + A full version of gtk-doc is now + made available. + However, some old software might not be capable of using + the current version of gtk-doc + to build documentation. + You need to change recipes that build such software so that + they explicitly disable building documentation with + gtk-doc. -- cgit v1.2.3-54-g00ecf