From faf19c5274a7966286e905e64d491cceb3992910 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 1 Apr 2015 14:45:26 -0700 Subject: ref-manual: Added new migration section for going to 1.8 (From yocto-docs rev: b8c7fad5404eb111c0d6a39fae6e9ffcb4a615ba) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/migration.xml | 231 +++++++++++++++++++++++++++++++++ 1 file changed, 231 insertions(+) (limited to 'documentation') diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml index 3dc141c552..f5c87bdd9e 100644 --- a/documentation/ref-manual/migration.xml +++ b/documentation/ref-manual/migration.xml @@ -2013,6 +2013,237 @@ +
+ Moving to the Yocto Project 1.8 Release + + + This section provides migration information for moving to the + Yocto Project 1.8 Release from the prior release. + + +
+ Removed Recipes + + + The following recipes have been removed: + + owl-video: + Functionality replaced by gst-player. + + gaku: + Functionality replaced by gst-player. + + gnome-desktop: + No longer needed. + + gsettings-desktop-schemas: + No longer needed. + + python-argparse: + The argparse module is already + provided in the default Python distribution in a + package named python-argparse. + Consequently, the separate + python-argparse recipe is no + longer needed. + + telepathy-python, libtelepathy, telepathy-glib, telepathy-idle, telepathy-mission-control: + All these recipes have moved to + meta-oe and are consequently no + longer needed by any recipes in OpenEmbedded-Core. + + linux-yocto_3.10 and linux-yocto_3.17: + Support for the linux-yocto 3.10 and 3.17 kernels has been + dropped. + Support for the 3.14 kernel remains, while support for + 3.19 kernel has been added. + + poky-feed-config-opkg: + No longer needed. + + libav 0.8.x: + libav 9.x is now used. + + sed-native: + No longer needed. + A working version of sed is expected + to be provided by the host distribution. + + + +
+ +
+ BlueZ 4.x / 5.x Selection + + + Proper built-in support for selecting BlueZ 5.x in preference + to the default of 4.x now exists. + To use BlueZ 5.x, simply add "bluez5" to your + DISTRO_FEATURES + value. + If you had previously added append files + (*.bbappend) to make this selection, you can + now remove them. + + + + Additionally, a + bluetooth + class has been added to make selection of the appropriate bluetooth + support within a recipe a little easier. + If you wish to make use of this class in a recipe, add something + such as the following: + + inherit bluetooth + PACKAGECONFIG ??= "${@bb.utils.contains('DISTRO_FEATURES', 'bluetooth', '${BLUEZ}', '', d)} + PACKAGECONFIG[bluez4] = "--enable-bluetooth,--disable-bluetooth,bluez4" + PACKAGECONFIG[bluez5] = "--enable-bluez5,--disable-bluez5,bluez5" + + +
+ +
+ SSL 3.0 is Now Disabled in OpenSSL + + + SSL 3.0 is now disabled when building OpenSSL. + Disabling SSL 3.0 avoids any lingering instances of the POODLE + vulnerability. + If you feel you must re-enable SSL 3.0, then you can add an + append file (*.bbappend) for the + openssl recipe to remove "-no-ssl3" + from + EXTRA_OECONF. + +
+ +
+ Default Sysroot Poisoning + + + gcc's default sysroot and include directories + are now "poisoned". + In other words, the sysroot and include directories are being + redirected to a non-existent location in order to catch when + host directories are being used due to the correct options not + being passed. + This poisoning applies both to the cross-compiler used within the + build and to the cross-compiler produced in the SDK. + + + + If this change causes something in the build to fail, it almost + certainly means the various compiler flags and commands are not + being passed correctly to the underlying piece of software. + In such cases, you need to take corrective steps. + +
+ +
+ Rebuild Improvements + + + Changes have been made to the + base, + autotools, + and + cmake + classes to clean out generated files when the + do_configure + task needs to be re-executed. + + + + One of the improvements is to attempt to run "make clean" during + the do_configure task if a + Makefile exists. + Some software packages do not provide a working clean target + within their make files. + If you have such recipes, you need to set + CLEANBROKEN + to "1". + + CLEANBROKEN = "1" + + +
+ +
+ QA Check and Validation Changes + + + The following QA Check and Validation Changes have occurred: + + + Usage of + PRINC + previously triggered a warning. + It now triggers an error. + You should remove any remaining usage of + PRINC in any recipe or append file. + + + An additional QA check has been added to detect usage of + ${D} in + FILES + values where + D values + should not be used at all. + The same check ensures that $D is used + in + pkg_preinst/pkg_postinst/pkg_prerm/pkg_postrm + functions. + + + S now + needs to be set to a valid value within a recipe. + If S is not set in the recipe, the + directory is not automatically created. + If S does not point to a directory + that exists at the time the + do_unpack + task finishes, a warning will be shown. + + + LICENSE + is now validated for correct formatting of multiple + licenses. + If the format is invalid (e.g. multiple licenses are + specified with no operators to specify how the multiple + licenses interact), then a warning will be shown. + + + +
+ +
+ Miscellaneous Changes + + + The following miscellaneous changes have occurred: + + + The send-error-report script now + expects a "-s" option to be specified before the server + address. + This assumes a server address is being specified. + + + The oe-pkgdata-util script now + expects a "-p" option to be specified before the + pkgdata directory, which is now + optional. + If the pkgdata directory is not + specified, the script will run BitBake to query + PKGDATA_DIR + from the build environment. + + + +
+
+