From 8d751c065d4ba958ebda1c9e1b3757f5ca582e09 Mon Sep 17 00:00:00 2001 From: Kristi Rifenbark Date: Mon, 7 May 2018 11:49:03 -0700 Subject: ref-manual: Added 2.5 Migration Section (From yocto-docs rev: 5d6c1b69e5559eced5142f46421302f61c95404c) Signed-off-by: Kristi Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/migration.xml | 417 +++++++++++++++++++++++++++++++++ 1 file changed, 417 insertions(+) (limited to 'documentation/ref-manual/migration.xml') diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml index 09f5f33de7..2998fbe437 100644 --- a/documentation/ref-manual/migration.xml +++ b/documentation/ref-manual/migration.xml @@ -5227,6 +5227,423 @@ id=f4d4f99cfbc2396e49c1613a7d237b9e57f06f81'>commit message. + +
+ Moving to the Yocto Project 2.5 Release + + + This section provides migration information for moving to the + Yocto Project 2.5 Release from the prior release. + + +
+ Packaging Changes + + + This section provides information about packaging changes that have + ocurred: + + + bind-libs: + The libraries packaged by the bind recipe are in a + separate bind-libs package. + + + libfm-gtk: + The libfm gtkpackage and bindings are + split into a separate libfm-gtk package. + + + flex-libfl: + The flex recipe splits out libfl into a separate + flex-libfl package to avoid too many + dependencies being pulled in where only the library is + needed. + + + grub-efi: + The grub-efi configuration is split + into a separate grub-bootconf + recipe. + However, the dependency relationship from + grub-efi is through a + virtual/grub-bootconf provider making it possible to have + your own recipe provide the dependency. + Alternatively, you can use a BitBake append file to bring + the configuration back into the + grub-efi recipe. + + + ARMv7-A Legacy Support: + Legacy support is removed for transitioning from ARMv7-A + to armv7a-vfp-neon in package feeds, which was previously + enabled by setting + PKGARCHCOMPAT_ARMV7A. + This transition occurred in 2011 and active package feeds + should by now be updated to the new naming. + + + +
+ +
+ Removed Recipes + + + The following recipes have been removed: + + + gcc: + The version 6.4 recipes are replaced by 7.x. + + + gst-player: + Renamed to gst-examples as per + upstream. + + + hostap-utils: + This recipe is obsolete. + + + latencytop: + This recipe is no longer maintained upstream. + The last release was in 2009. + + + libpfm4: + The only file that requires this recipe is + oprofile, which has been removed. + + + linux-yocto: + The version 4.4, 4.9, and 4.10 recipes have been removed. + Versions 4.12, 4.14, and 4.15 remain. + + + man: + This recipe has been replaced by + modern man-db + + + mkelfimage: + This recipe has been removed in the upstream coreboot, + and is no longer needed with the removal of the ELF image + type. + + + nativesdk-postinst-intercept: + This recipe is not maintained. + + + neon: + This recipe is not maintained upstream and is not used by + anything in OpenEmbedded-Core. + + + oprofile: + The functionality of this recipe is replaced by + perf since keeping ongoing + compatibility on with musl is + difficult. + + + pax: + This recipe is obsolete. + + + stat: + This recipe is not maintained upstream. + coreutils provides a modern binary for + the stat recipe. + + + zisofs-tools-native: + This recipe is no longer needed because the compressed + ISO image feature has been removed. + + + +
+ + + + + + + + + + + + + + + + + + + + +
+ Scripts and Tools Changes + + + The following are changes to scripts and tools: + + + yocto-bsp, + yocto-kernel, and + yocto-layer: + The yocto-bsp, + yocto-kernel, and + yocto-layer scripts previously shipped + with poky but not in OpenEmbedded-Core have been removed. + These scripts are not maintained and are outdated. + In many cases, they are also limited in scope. + The bitbake-layers create-layer command + is a direct replacement for yocto-layer. + See the documentation to create a BSP or kernel recipe in + the + "BSP Kernel Recipe Example" + section. + + + devtool finish: + will now exit with an error if there are uncommitted changes + or a rebase/am in progress in the source repository for the + recipe, as it may indicate that you have forgotten to + commit some changes (and thus these would not be reflected + in updates to the patches applied by the recipe). + A -f/--force option is provided for situations where you + know that those uncomitted changes are inconsequential and + wish to proceed regardless. + + + scripts/oe-setup-rpmrepo script: + has been removed as its functionality can be replaced by + bitbake package-index. + + + scripts/test-dependencies.sh script: + has been removed as it was largely made obsolete by the + recipe-specific sysroots functionality introduced in the + previous release. + + + +
+ +
+ BitBake Changes + + + The following are changes BitBake: + + + The --runall option has changed behaviour slightly. + There are in fact two different behaviours people may want: + + + For a given target (or set of targets) look through + the task graph and run task X only if its present + and would have been built. + + + For a given target (or set of targets) look through + the task graph and run task X if any recipe in the + taskgraph has such a target even if it wasn't in the + original task graph. + + + The --runall option now performs (b), previously it behaved + like (a). A --runonly option has been added to retain the + ability to perform (a). + + + Several explicit "run this task for all recipes in the + dependency tree" tasks (such as fetchall, checkuriall, and + the *all tasks provided by the distrodata and archiver + classes) have now been removed as there is a bitbake option + to do this for any arbitrary task, for example: + + bitbake <target> -c fetchall + + should now be replaced with: + + bitbake <target> --runall=fetch + + + + +
+ + +
+ Miscellaneous Changes + + + The following are additional changes: + + + The kernel class now supports building packages for multiple + kernels. If your kernel recipe/bbappend mentions packaging + at all, then you are advised to replace references to kernel + in package names with ${KERNEL_PACKAGE_NAME}. For example, + if you disable automatic installation of the kernel image + using RDEPENDS_kernel-base = "" then to avoid warnings you + will now need to use + RDEPENDS_${KERNEL_PACKAGE_NAME}-base = "" instead. + + + The buildhistory class now commits changes to the repository + by default, so setting BUILDHISTORY_COMMIT = "1" is no + longer necessary. If you wish commits to be disabled, then + you will now need to set BUILDHISTORY_COMMIT = "0" in your + configuration. + + + The beaglebone reference machine has been renamed to + beaglebone-yocto. The beaglebone-yocto BSP is a reference + implementation using only mainline components available in + OpenEmbedded-Core and meta-yocto-bsp, whereas Texas + Instruments maintain a full-featured BSP in the meta-ti + layer, and the rename avoids the previous name clash that + existed between the two BSPs. + + + The update-alternatives class will now no longer work with + SysV init scripts as such usage has been proven to be + problematic. + Related to this, the sysklogd recipe no longer uses + update-alternatives as it is incompatible with other + implementations. + + + The cmake class now uses ninja instead of make by default + for building in order to improve build performance. If a + recipe is broken with ninja then the recipe can set + OECMAKE_GENERATOR = "Unix Makefiles" to change back to make. + + + python: Restructure python packaging and replace it with + autopackaging + + + python3: Restructure python3 packaging and replace it with + autopackaging + + + The previously deprecated base_* functions have now removed, + in favour of their replacements in meta/lib/oe and + bitbake/lib/bb. + These are typically used from recipes and classes and any + references to the old functions will now need to be updated. + The full list along with each of their replacements: + + + base_path_join() -> oe.path.join() + + base_path_relative() -> oe.path.relative() + + base_path_out() -> oe.path.format_display() + + + base_read_file() -> oe.utils.read_file() + + + base_ifelse() -> oe.utils.ifelse() + + + base_conditional() -> oe.utils.conditional() + + + base_less_or_equal() -> oe.utils.less_or_equal() + + + base_version_less_or_equal() -> oe.utils.version_less_or_equal() + + + base_contains() -> bb.utils.contains() + + + base_both_contain() -> oe.utils.both_contain() + + + base_prune_suffix() -> oe.utils.prune_suffix() + + + oe_filter() -> oe.utils.str_filter() + + + oe_filter_out() -> oe.utils.str_filter_out() + (or use the _remove operator) + + + + + Using exit 1 as a means of explicitly deferring a + postinstall script until first boot is now deprecated, as + it is not an obvious mechanism and can mask actual errors. + If you want to explicitly defer a postinstall to first boot + on the target rather than possibly at rootfs creation time, + use pkg_postinst_ontarget() or alternatively call + postinst-intercepts defer_to_first_boot from pkg_postinst(). + Any failure of a pkg_postinst() script (including exit 1) + will now trigger a warning during do_rootfs. + + + The elf image type has been removed, as the mkelfimage tool + that was required to create it is no longer provided by + coreboot upstream, and required updating every time binutils + got updated. + + + Support for .iso image compression (previously enabled via + COMPRESSISO = "1") has been removed, since the userspace + tools (zisofs-tools) are unmaintained and squashfs provides + better performance and compression. + In order to build a live image with squashfs+lz4 compression + enabled you would set LIVE_ROOTFS_TYPE = "squashfs-lz4" + and ensure that live is in IMAGE_FSTYPES. + + + Recipes having an unconditional dependency on libpam will + now only be buildable with pam in DISTRO_FEATURES. + If the dependency is truly optional then it is recommended + that the dependency be made conditional upon pam being in + DISTRO_FEATURES. + + + For EFI-based machines, the bootloader (grub-efi by default) + is now installed into the image at /boot. wic can be used to + split this into separate boot and rootfs partitions if + desired. + + + Patches whose context does not match exactly (i.e. where + patch reports "fuzz" when applying) will now generate a + warning. + See http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=cc97bc08125b63821ce3f616771830f77c456f57 + + + Layers are now expected to set LAYERSERIES_COMPAT_layername + to match the version(s) of OpenEmbedded-Core they are + compatible with (specified as codenames using spaces to + separate multiple values, e.g. "rocko sumo"). + If a layer does not set this, a warning will be shown. + If a layer sets a value that does not include the current + version, then an error will be produced. + + + The TZ environment variable is now set to "UTC" within the + build environment in order to fix reproducibility problems + in some recipes. + + + +
+