Download build/tmp/deploy

Migrating to a Newer Yocto Project Release
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 [http://www.yoctoproject.org/docs/1.4.2/
dev-manual/dev-manual.html#source-repositories].
4.2. 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.
4.2.1. BitBake
Differences include the following:
• Comment Continuation: If a comment ends with a line continuation (\) character, then the next line
must also be a comment. Any instance where this is not the case, now triggers a warning. You must
either remove the continuation character, or be sure the next line is a comment.
• Package Name Overrides: The runtime package specific variables RDEPENDS, RRECOMMENDS,
RSUGGESTS, RPROVIDES, RCONFLICTS, RREPLACES, FILES, ALLOW_EMPTY, and the pre, post, install,
and uninstall script functions pkg_preinst, pkg_postinst, pkg_prerm, and pkg_postrm should
always have a package name override. For example, use RDEPENDS_${PN} for the main package
instead of RDEPENDS. BitBake uses more strict checks when it parses recipes.
4.2.2. Build Behavior
Differences include the following:
• Shared State Code: The shared state code has been optimized to avoid running unnecessary tasks.
For example, bitbake -c rootfs some-image from shared state no longer populates the target
sysroot since that is not necessary. Instead, the system just needs to extract the output package
contents, re-create the packages, and construct the root filesystem. This change is unlikely to cause
any problems unless you have missing declared dependencies.
• Scanning Directory Names: When scanning for files in SRC_URI, the build system now uses
FILESOVERRIDES instead of OVERRIDES for the directory names. In general, the values previously in
OVERRIDES are now in FILESOVERRIDES as well. However, if you relied upon an additional value you
previously added to OVERRIDES, you might now need to add it to FILESOVERRIDES unless you are
already adding it through the MACHINEOVERRIDES or DISTROOVERRIDES variables, as appropriate.
For more related changes, see the "Variables" section.
4.2.3. 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 the meta-yocto/conf/site.conf.sample file for information on how
to use this script.
4.2.4. Custom Interfaces File (netbase change)
If you have created your own custom etc/network/interfaces file by creating an append file
for the netbase recipe, you now need to create an append file for the init-ifupdown recipe
instead, which you can find in the Source Directory [http://www.yoctoproject.org/docs/1.4.2/devmanual/dev-manual.html#source-directory] at meta/recipes-core/init-ifupdown. For information
on how to use append files, see the "Using .bbappend Files [http://www.yoctoproject.org/docs/1.4.2/
dev-manual/dev-manual.html#using-bbappend-files]" in the Yocto Project Development Manual.
4.2.5. Remote Debugging
Support for remote debugging with the Eclipse IDE is now separated into an image feature (eclipsedebug) that corresponds to the packagegroup-core-eclipse-debug package group. Previously, the
30