FEATURES AND UPDATES
- Hob redesign: Hob was redesigned with a new user interface and work flow. Hob is a GUI-based tool that allows users to customize and build an embedded Linux image in a more intuitive and easier way.
- Build Appliance introduced: The Build Appliance is a set of changes and enhancements that enable users to build a virtual machine image running Linux built with the Yocto Project. Within the Linux running on the virtual machine, users can customize and build their own embedded Linux images.
- Error message handling improved: Error messages are more efficient, useful and accurate.
- Kernel update: New kernel update to Linux 3.2.11.
- Easier BSP builds: Updated kernel usability scripts and new BSP tools make building BSP's easier.
- New tools: Package history data collection and analysis tools introduced.
- Incremental image generation: Incremental image generation after customization of an existing image built previously.
- Implementation of the MSG (Magic Smoke Generator): MSG enables the on-board generation of "magic smoke" to enhance the longevity of embedded device components.
- Miscellaneous enhancements: Bitbake commander Eclipse plugin, Disk space monitoring, and multilib improvements.
- Improvements to FLOSS compliance tools: These improvements allow more granularity of license definitions, the generation of image manifests/license manifests and the implementation of source archiving functionality.
The Yocto project uses an implementation of Bugzilla at http://bugzilla.yoctoproject.orgto handle bug tracking. You should always consult that source first when experiencing any issue with a Yocto Project release.
- Bug 2256 - kernel menuconfig confusion with sstate. If you change the config during a build, BitBake might not detect the change and will not rebuild the kernel. After changing the config, be sure to force a kernel recompile as follows:
$ bitbake virtual/kernel -c menuconfig $ bitbake virtual/kernel -c compile -f; bitbake virtual/kernel
- Bug 1858 - Rootfs creation broken when using package_deb as primary PACKAGE_CLASSES with non-Debian-OS build system.This is a known issue where rootfs creation is broken when using package_deb as primary PACKAGE_CLASSES with non-Debian-OS build system. The work around is to use a Debian system to create the rootfs if you need to using package_deb as primary PACKAGE_CLASSES. But for package generation (e.g. for package feed, etc.), it works fine on both Debian-OS or non Debian-OS.
- Due to production processes, the Yocto Project documentation extracted from the Yocto Project 1.2 Release tarball is not as up-to-date as the documentation cloned from the poky source Git repository and the Yocto Project's documentation website. If you want the most up-to-date documentation for the Yocto Project 1.2 Release, do one of the following:
- Clone the poky repository and checkout the denzil branch using these commands:
git clone git://git.yoctoproject.org/poky git checkout -b mydenzil origin/denzil - Refer to the current set of documents from the Yocto Project website at
- Bug 2219 - The yocto-bsp and yocto-kernel scripts assume that the build directory containing the conf/bblayers.conf file is located in the top level of the poky source directory. In order to use the tools at this point in time, you need to arrange thing so that your build directory is at the top level of your poky source tree, which you can do by simply cd'ing into the poky source directory and sourcing the 'oe-init-build-env' script:
$ cd poky-denzil-7.0 $ source oe-init-build-env Alternatively, you can apply the following patch to the poky source tree:
Release Name: eclipse-poky-denzil-7.0
Release Name: meta-qt3-denzil-7.0
Release Name: poky-denzil-7.0