%poky; ] > Migrating to a Newer Yocto Project Release This chapter provides information you can use to migrate work to a newer Yocto Project release. You can find the same information in the release notes for a given release.
Moving to the Yocto Project 1.3 Release This section provides migration information for moving to the Yocto Project 1.3 Release from the prior release.
Local Configuration Differences include changes for SSTATE_MIRRORS and bblayers.conf.
SSTATE_MIRRORS The shared state cache (sstate-cache), as pointed to by SSTATE_DIR, by default now has two-character subdirectories to prevent issues rising from too many files in the same directory. Also, native sstate-cache packages will go into a subdirectory named using the distro ID string. If you copy the newly structured sstate-cache to a mirror location (either local or remote) and then point to it in SSTATE_MIRRORS, you need to append "PATH" to the end of the mirror URL so that the path used by BitBake before the mirror substitution is appended to the path used to access the mirror. Here is an example: SSTATE_MIRRORS = "file://.* http://someserver.tld/share/sstate/PATH"
bblayers.conf The meta-yocto layer consists of two parts that correspond to the Poky reference distribution and the reference hardware Board Support Packages (BSPs), respectively: meta-yocto and meta-yocto-bsp. When running BitBake or Hob for the first time after upgrading, your conf/bblayers.conf file will be updated to handle this change and you will be asked to re-run or restart for the changes to take effect.
Recipes Differences include changes for the following: Python function whitespace proto= in SRC_URI nativesdk Task recipes IMAGE_FEATURES Removed recipes
Python Function Whitespace All Python functions must now use four spaces for indentation. Previously, an inconsistent mix of spaces and tabs existed, which made extending these functions using _append or _prepend complicated given that Python treats whitespace as syntactically significant. If you are defining or extending any Python functions (e.g. populate_packages, do_unpack, do_patch and so forth) in custom recipes or classes, you need to ensure you are using consistent four-space indentation.
proto= in SRC_URI Any use of proto= in SRC_URI needs to be changed to protocol=. In particular, this applies to the following URIs: svn:// bzr:// hg:// osc:// Other URIs were already using protocol=. This change improves consistency.
nativesdk The suffix nativesdk is now implemented as a prefix, which simplifies a lot of the packaging code for nativesdk recipes. All custom nativesdk recipes and any references need to be updated to use nativesdk-* instead of *-nativesdk.
Task Recipes "Task" recipes are now known as "Package groups" and have been renamed from task-*.bb to packagegroup-*.bb. Existing references to the previous task-* names should work in most cases as there is an automatic upgrade path for most packages. However, you should update references in your own recipes and configurations as they could be removed in future releases. You should also rename any custom task-* recipes to packagegroup-*, and change them to inherit packagegroup instead of task, as well as taking the opportunity to remove anything now handled by packagegroup.bbclass, such as providing -dev and -dbg packages, setting LIC_FILES_CHKSUM, and so forth. See the "Package Groups - packagegroup.bbclass" section for further details.
IMAGE_FEATURES Image recipes that previously included "apps-console-core" in IMAGE_FEATURES should now include "splash" instead to enable the boot-up splash screen. Retaining "apps-console-core" will still include the splash screen but generates a warning. The "apps-x11-core" and "apps-x11-games" IMAGE_FEATURES features have been removed.
Removed Recipes The following recipes have been removed. For most of them, it is unlikely that you would have any references to them in your own Metadata. However, you should check your metadata against this list to be sure: libx11-trim: Replaced by libx11, which has a negligible size difference with modern Xorg. xserver-xorg-lite: Use xserver-xorg, which has a negligible size difference when DRI and GLX modules are not installed. xserver-kdrive: Effectively unmaintained for many years. mesa-xlib: No longer serves any purpose. galago: Replaced by telepathy. gail: Functionality was integrated into GTK+ 2.13. eggdbus: No longer needed. gcc-*-intermediate: The build has been restructured to avoid the need for this step. libgsmd: Unmaintained for many years. Functionality now provided by ofono instead. contacts, dates, tasks, eds-tools: Largely unmaintained PIM application suite. It has been moved to meta-gnome in meta-openembedded. In addition to the previously listed changes, the meta-demoapps directory has also been removed because the recipes in it were not being maintained and many had become obsolete or broken. Additionally, these recipes were not parsed in the default configuration. Many of these recipes are already provided in an updated and maintained form within the OpenEmbedded community layers such as meta-oe and meta-gnome. For the remainder, you can now find them in the meta-extras repository, which is in the Yocto Project Source Repositories.
Moving to the Yocto Project 1.4 Release This section provides migration information for moving to the Yocto Project 1.4 Release from the prior release. Here is the raw text from Paul: * BitBake - Fix continuation on last line of a comment: if a comment ends in a line continuation (\) then the next line must also be a comment; any instance where this is not the case will now trigger a warning. Either remove the continuation character or make the next line a comment as well. * BitBake - The runtime package specific variables (RDEPENDS, RRECOMMENDS, RSUGGESTS, RPROVIDES, RCONFLICTS, RREPLACES, FILES, ALLOW_EMPTY, and the pre/post install/uninstall script functions pkg_preinst, pkg_postinst, pkg_prerm, and pkg_postrm) should always have a package name override, for example RDEPENDS_${PN} for the main package instead of RDEPENDS; there are now stricter checks at parse time to ensure this is done in all recipes. * Build Behavior - Shared state code has been optimised to avoid running tasks that are not really needed; for example, bitbake -c rootfs some-image from shared state will no longer populate the target sysroot since that is not necessary - the system just needs to extract the output package contents, re-create the packages and construct the root filesystem. This is unlikely to cause any problems unless you have missing declared dependencies. * Proxies and Fetching Source - A new oe-git-proxy script has been added to replace previous methods of handling proxies and fetching source from Git. See meta-yocto/conf/site.conf.sample for information on how to use this script. * Build Behavior - When scanning for files in SRC_URI, the system now uses FILESOVERRIDES instead of OVERRIDES for the directory names. All of the sensible values previously in OVERRIDES are now in FILESOVERRIDES as well, however if you relied upon an additional value you added to OVERRIDES you may now need to add it to FILESOVERRIDES (unless you are already adding it via the MACHINEOVERRIDES or DISTROOVERRIDES variables, where this is appropriate). * Remote Debugging - Support for remote debugging with the Eclipse IDE has been split out into a separate image feature (eclipse-debug) corresponding to the packagegroup-core-eclipse-debug package group. (Previously this was included in the tools-debug image feature which corresponds to the packagegroup-core-tools-debug package group.) * Variables - SANITY_TESTED_DISTROS now uses a distro ID composed of the host distributor ID followed by the release, rather than the description field being used previously (so "Ubuntu 12.10" becomes "Ubuntu-12.10"). If you aren't setting this variable (or are setting it to "") you don't need to worry about this. * Items Removed - mesa-dri renamed to mesa - Gtk+ DirectFB support has been removed since it is no longer supported in upstream Gtk+ as of version 2.18 - linux-yocto 3.0 kernel has been removed and a version 3.8 has been added - mesa-xlib removed - no longer useful - polkit removed - now in the meta-oe layer - libmusicbrainz removed - now in the meta-multimedia layer - zeroconf removed - now in the meta-networking layer - web removed - unmaintained and superseded by web-webkit - gtkhtml2 removed - now in the meta-oe layer - clutter-box2d removed - now in the meta-oe layer - orinoco-conf removed - obsolete - matchbox-stroke removed - was never more than a proof-of-concept - update-modules removed - no longer used (kernel module postinstall/postrm scripts can now do the same task without the use of this script) - zypper / libzypp / sat-solver removed - these have been functionally replaced with Smart (python-smartpm) when RPM packaging is used and package management is enabled on the target. - libcanberra removed - now in the meta-gnome layer - metacity removed - now in the meta-gnome layer - gupnp removed - now in the meta-multimedia layer - libgdata removed - now in the meta-gnome layer - gthumb removed - now in the meta-gnome layer - mutter removed - never used by anything else and recipe was very old - gypsy removed - now in the meta-oe layer - matchbox-wm-2 / matchbox-theme-sato-2 removed - unmaintained (matchbox-wm / matchbox-theme-sato still provided) - lsbsetup removed - functionality now provided by lsbtest - evolution-data-server removed - now in the meta-gnome layer - xf86bigfontproto removed - disabled by default upstream since 2007, nothing uses it - evieext removed - removed from xserver in 2008 - xf86rushproto removed - dependency in xserver was spurious and was removed in 2005 - libxfontcache / xfontcacheproto removed - removed from the Xorg server in 2008 - libxp / libxprintapputil / libxprintutil / printproto removed - the XPrint server was removed from Xorg in 2008 - libxtrap / xtrapproto removed - functionality was broken upstream so it was removed