Release 1.5 (dora)
This section provides migration information for moving to the Yocto Project 1.5 Release (codename “dora”) from the prior release.
Host Dependency Changes
The OpenEmbedded build system now has some additional requirements on the host system:
Patched version of Make if you are using 3.82. Most distributions that provide Make 3.82 use the patched version.
If the Linux distribution you are using on your build host does not provide packages for these, you can install and use the Buildtools tarball, which provides an SDK-like environment containing them.
For more information on this requirement, see the “Required Git, tar, Python, make and gcc Versions” section.
atom-pc Board Support Package (BSP)
atom-pc hardware reference BSP has been replaced by a
genericx86 BSP. This BSP is not necessarily guaranteed to work on
all x86 hardware, but it will run on a wider range of systems than the
genericx86-64 BSP has been added for 64-bit Atom
The following changes have been made that relate to BitBake:
BitBake now supports a
_removeoperator. The addition of this operator means you will have to rename any items in recipe space (functions, variables) whose names currently contain
_remove_or end with
_removeto avoid unexpected behavior.
BitBake’s global method pool has been removed. This method is not particularly useful and led to clashes between recipes containing functions that had the same name.
The “none” server backend has been removed. The “process” server backend has been serving well as the default for a long time now.
bitbake-runtaskscript has been removed.
}are no longer added to PROVIDES by default in
bitbake.conf. These version-specific PROVIDES items were seldom used. Attempting to use them could result in two versions being built simultaneously rather than just one version due to the way BitBake resolves dependencies.
The following changes have been made to the package QA checks:
If you have customized ERROR_QA or WARN_QA values in your configuration, check that they contain all of the issues that you wish to be reported. Previous Yocto Project versions contained a bug that meant that any item not mentioned in ERROR_QA or WARN_QA would be treated as a warning. Consequently, several important items were not already in the default value of WARN_QA. All of the possible QA checks are now documented in the “insane.bbclass” section.
An additional QA check has been added to check if
/usr/share/info/diris being installed. Your recipe should delete this file within do_install if “make install” is installing it.
If you are using the buildhistory class, the check for the package version going backwards is now controlled using a standard QA check. Thus, if you have customized your ERROR_QA or WARN_QA values and still wish to have this check performed, you should add “version-going-backwards” to your value for one or the other variables depending on how you wish it to be handled. See the documented QA checks in the “insane.bbclass” section.
Directory Layout Changes
The following directory changes exist:
Output SDK installer files are now named to include the image name and tuning architecture through the SDK_NAME variable.
Images and related files are now installed into a directory that is specific to the machine, instead of a parent directory containing output files for multiple machines. The DEPLOY_DIR_IMAGE variable continues to point to the directory containing images for the current MACHINE and should be used anywhere there is a need to refer to this directory. The
runqemuscript now uses this variable to find images and kernel binaries and will use BitBake to determine the directory. Alternatively, you can set the DEPLOY_DIR_IMAGE variable in the external environment.
When buildhistory is enabled, its output is now written under the Build Directory rather than TMPDIR. Doing so makes it easier to delete TMPDIR and preserve the build history. Additionally, data for produced SDKs is now split by IMAGE_NAME.
pkgdatadirectory produced as part of the packaging process has been collapsed into a single machine-specific directory. This directory is located under
sysrootsand uses a machine-specific name (i.e.
BitBake will now shorten revisions from Git repositories from the normal 40 characters down to 10 characters within SRCPV for improved usability in path and filenames. This change should be safe within contexts where these revisions are used because the chances of spatially close collisions is very low. Distant collisions are not a major issue in the way the values are used.
The following changes have been made that relate to IMAGE_FEATURES:
The value of IMAGE_FEATURES is now validated to ensure invalid feature items are not added. Some users mistakenly add package names to this variable instead of using IMAGE_INSTALL in order to have the package added to the image, which does not work. This change is intended to catch those kinds of situations. Valid IMAGE_FEATURES are drawn from
PACKAGE_GROUPdefinitions, COMPLEMENTARY_GLOB and a new “validitems” varflag on IMAGE_FEATURES. The “validitems” varflag change allows additional features to be added if they are not provided using the previous two mechanisms.
The previously deprecated “apps-console-core” IMAGE_FEATURES item is no longer supported. Add “splash” to IMAGE_FEATURES if you wish to have the splash screen enabled, since this is all that apps-console-core was doing.
/run directory from the Filesystem Hierarchy Standard 3.0 has
been introduced. You can find some of the implications for this change
The change also means that recipes that install files to
must be changed. You can find a guide on how to make these changes
Removal of Package Manager Database Within Image Recipes
core-image-minimal no longer adds
This addition is now handled automatically when “package-management” is
not in IMAGE_FEATURES. If you have custom
image recipes that make this addition, you should remove the lines, as
they are not needed and might interfere with correct operation of
Images Now Rebuild Only on Changes Instead of Every Time
The do_rootfs and other related image construction tasks are no longer marked as “nostamp”. Consequently, they will only be re-executed when their inputs have changed. Previous versions of the OpenEmbedded build system always rebuilt the image when requested rather when necessary.
The previously deprecated
task.bbclass has now been dropped. For
recipes that previously inherited from this class, you should rename
packagegroup-* and inherit packagegroup
For more information, see the “packagegroup.bbclass” section.
By default, we now split BusyBox into two binaries: one that is suid
root for those components that need it, and another for the rest of the
components. Splitting BusyBox allows for optimization that eliminates
tinylogin recipe as recommended by upstream. You can disable
this split by setting
BUSYBOX_SPLIT_SUID to “0”.
Automated Image Testing
A new automated image testing framework has been added through the
testimage*.bbclass classes. This
framework replaces the older
You can learn more about performing automated image tests in the “Performing Automated Runtime Testing” section in the Yocto Project Development Tasks Manual.
Following are changes to Build History:
Installed package sizes:
installed-package-sizes.txtfor an image now records the size of the files installed by each package instead of the size of each compressed package archive file.
The dependency graphs (
depends*.dot) now use the actual package names instead of replacing dashes, dots and plus signs with underscores.
buildhistory-collect-srcrevsutilities have improved command-line handling. Use the
--helpoption for each utility for more information on the new syntax.
For more information on Build History, see the “Maintaining Build Output Quality” section in the Yocto Project Development Tasks Manual.
Following are changes to
udevno longer brings in
udev-extraconfautomatically through RRECOMMENDS, since this was originally intended to be optional. If you need the extra rules, then add
udev-extraconfto your image.
udevno longer brings in
usbutils-idsthrough RRECOMMENDS. These are not needed by
udevitself and removing them saves around 350KB.
Removed and Renamed Recipes
linux-yocto3.2 kernel has been removed.
libtool-nativesdkhas been renamed to
tinyloginhas been removed. It has been replaced by a suid portion of Busybox. See the “BusyBox” section for more information.
external-python-tarballhas been renamed to
web-webkithas been removed. It has been functionally replaced by
imakehas been removed. It is no longer needed by any other recipe.
transfig-nativehas been removed. It is no longer needed by any other recipe.
anjuta-remote-runhas been removed. Anjuta IDE integration has not been officially supported for several releases.
Following is a list of short entries describing other changes:
run-postinsts: Make this generic.
base-files: Remove the unnecessary
alsa-state: Provide an empty
classes/image: Ensure BAD_RECOMMENDATIONS supports pre-renamed package names.
classes/rootfs_rpm: Implement BAD_RECOMMENDATIONS for RPM.
systemdis not in DISTRO_FEATURES.
systemdunit file is present and
sysvinitis not a distro feature.
libpam: Deny all services for the
linux-dtb: Use kernel build system to generate the
kern-tools: Switch from guilt to new