From 7814b33b5678a3a17b6c49e62b5a37958e57f1a3 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 7 Jan 2016 18:17:07 -0600 Subject: ref-manual: Updates to cull out qt4 stuff. Several areas changed throughout the ref-manual to remove qt4 referencing. (From yocto-docs rev: 9ee721034ceb2bb7b7a9e64f6a6a7a2b3bfd1c82) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/migration.xml | 25 +++++++++++ documentation/ref-manual/ref-classes.xml | 60 -------------------------- documentation/ref-manual/ref-features.xml | 3 -- documentation/ref-manual/ref-images.xml | 3 -- documentation/ref-manual/ref-structure.xml | 8 ---- documentation/ref-manual/ref-tasks.xml | 9 ---- documentation/ref-manual/ref-variables.xml | 9 ++-- documentation/ref-manual/technical-details.xml | 7 +-- 8 files changed, 32 insertions(+), 92 deletions(-) diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml index 21763e3a46..45ac041d92 100644 --- a/documentation/ref-manual/migration.xml +++ b/documentation/ref-manual/migration.xml @@ -2735,6 +2735,31 @@ +
+ Moving to the Yocto Project 2.1 Release + + + This section provides migration information for moving to the + Yocto Project 2.1 Release from the prior release. + + +
+ Stuff to Remember When Creating this Section + + + This is a note from Alexander Kanavin regarding qt4 stuff. + + Qt4 recipes and classes have been removed in YP 2.1 because + Qt4.x has reached end of life upstream. For legacy applications + and LSB compliancy purposes Qt4 can be found in meta-qt4 + repository, and for any new development Qt5 is available at + meta-qt5 repository(provide links to both). + + +
+
+ + - The toolchain binary prefix used for nativesdk recipes. + The toolchain binary prefix used for + nativesdk recipes. The OpenEmbedded build system uses the SDK_PREFIX value to set the TARGET_PREFIX diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml index 2df36521c2..bd4ad8f21f 100644 --- a/documentation/ref-manual/technical-details.xml +++ b/documentation/ref-manual/technical-details.xml @@ -1378,7 +1378,6 @@ COMMERCIAL_AUDIO_PLUGINS ?= "" COMMERCIAL_VIDEO_PLUGINS ?= "" - COMMERCIAL_QT = "" If you want to enable these components, you can do so by making sure you have statements similar to the following @@ -1388,7 +1387,6 @@ gst-plugins-ugly-mpegaudioparse" COMMERCIAL_VIDEO_PLUGINS = "gst-plugins-ugly-mpeg2dec \ gst-plugins-ugly-mpegstream gst-plugins-bad-mpegvideoparse" - COMMERCIAL_QT ?= "qmmp" LICENSE_FLAGS_WHITELIST = "commercial_gst-plugins-ugly commercial_gst-plugins-bad commercial_qmmp" Of course, you could also create a matching whitelist @@ -1406,9 +1404,8 @@ Specifying audio and video plug-ins as part of the COMMERCIAL_AUDIO_PLUGINS and COMMERCIAL_VIDEO_PLUGINS statements - or commercial Qt components as part of - the COMMERCIAL_QT statement (along - with the enabling LICENSE_FLAGS_WHITELIST) includes the + (along with the enabling + LICENSE_FLAGS_WHITELIST) includes the plug-ins or components into built images, thus adding support for media formats or components. -- cgit v1.2.3-54-g00ecf