[oe] [meta-oe][PATCH] xmlstarlet: add newrecipe for version 1.5.0
Useful CLI tool for XML data manipulation.
Signed-off-by: Matthieu Crapet matthieu.cra...@ingenico.com
---
.../xmlstarlet/files/configure.ac.patch| 28 ++
.../recipes-support/xmlstarlet/xmlstarlet_1.5.0.bb | 25 +++
2 files changed, 53 insertions(+)
create mode 100644 meta-oe/recipes-support/xmlstarlet/files/configure.ac.patch
create mode 100644 meta-oe/recipes-support/xmlstarlet/xmlstarlet_1.5.0.bb
diff --git a/meta-oe/recipes-support/xmlstarlet/files/configure.ac.patch
b/meta-oe/recipes-support/xmlstarlet/files/configure.ac.patch
new file mode 100644
index 000..e55f4f3
--- /dev/null
+++ b/meta-oe/recipes-support/xmlstarlet/files/configure.ac.patch
@@ -0,0 +1,28 @@
+configure.ac: don't use xml-config if --with-libxml-prefix is specified to
configure
+
+Same behavior for xslt-config.
+
+diff --git a/configure.ac b/configure.ac
+index ed04e0c..39d5d4c 100644
+--- a/configure.ac
b/configure.ac
+@@ -40,7 +40,8 @@ AC_ARG_PROGRAM dnl Transforming Program Names When
Installing
+ AC_PROG_SED
+ AC_PROG_AWK
+
+-XSTAR_LIB_CHECK([LIBXML], [xml2-config])
++AS_IF([test x$LIBXML_PREFIX = x],
++ [XSTAR_LIB_CHECK([LIBXML], [xml2-config])])
+
+ AS_IF([test x$LIBXML_SRCDIR != x],
+ [LIBXML_INCDIR=$LIBXML_SRCDIR/include])
+@@ -56,7 +57,8 @@ AS_IF([test x$STATIC_LIBS != xno],
+ [LIBXML_LDFLAGS=-L$LIBXML_LIBDIR]
+
+
+-XSTAR_LIB_CHECK([LIBXSLT], [xslt-config])
++AS_IF([test x$LIBXSLT_PREFIX = x],
++ [XSTAR_LIB_CHECK([LIBXSLT], [xslt-config])])
+
+ AS_IF([test x$LIBXSLT_SRCDIR != x],
+ [XSLTPROC_PATH=$LIBXSLT_SRCDIR/xsltproc:$PATH
diff --git a/meta-oe/recipes-support/xmlstarlet/xmlstarlet_1.5.0.bb
b/meta-oe/recipes-support/xmlstarlet/xmlstarlet_1.5.0.bb
new file mode 100644
index 000..770ccab
--- /dev/null
+++ b/meta-oe/recipes-support/xmlstarlet/xmlstarlet_1.5.0.bb
@@ -0,0 +1,25 @@
+SUMMARY = Command line XML toolkit
+DESCRIPTION = XMLStarlet is a command line XML toolkit which can be used to \
+ transform, query, validate, and edit XML documents and files \
+ using simple set of shell commands in similar way it is done \
+ for plain text files using grep/sed/awk/tr/diff/patch.
+HOMEPAGE = http://xmlstar.sourceforge.net/;
+BUGTRACKER = http://xmlstar.sourceforge.net/bugs/;
+
+SECTION = console/utils
+LICENSE = MIT
+LIC_FILES_CHKSUM = file://COPYING;md5=c04760d09e8b0fe73283d0cc9e8bea53
+
+DEPENDS = libxml2 libxslt
+
+SRC_URI = ${SOURCEFORGE_MIRROR}/xmlstar/${BPN}-${PV}.tar.gz \
+ file://configure.ac.patch
+SRC_URI[md5sum] = 0c6db295d0cf9ff0d439edb755b7e8f6
+SRC_URI[sha256sum] =
47b4ed042ea2909257f2a386001af49fceb303f84da7214779ccf99fffc6bbba
+
+inherit autotools
+
+# doc build: requires (native) xstlproc, fop, pdf2ps
+EXTRA_OECONF=--disable-build-docs \
+ --with-libxml-prefix=${STAGING_LIBDIR}/.. \
+ --with-libxslt-prefix=${STAGING_LIBDIR}/..
--
1.8.5.4
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-qt5][PATCH] qmake5_base.bbclass: Use Qt version specific paths
On Thu, Feb 20, 2014 at 4:50 AM, Urs Fässler u...@bytesatwork.ch wrote: On Mit, 2014-02-19 at 16:11 -0300, Otavio Salvador wrote: On Wed, Feb 19, 2014 at 12:22 AM, Otavio Salvador ota...@ossystems.com.br wrote: When looking for Qt5 components and files we ought to use the Qt5 specific path. In case the distribution wants to have a flat tree it can set QT_DIR_NAME and it will still works as expected. Signed-off-by: Otavio Salvador ota...@ossystems.com.br --- I have built two image and the SDK from scratch using this with no issues. Could someone also give this a try? Today I rebuilt 5.2.1 image and SDK in two build machines (one Debian Sid and another Debian 7.4 based) and both succeed. Did someone try this one? I successfully built Qt 5.2.1 (from the 5.2.1 repository, not the above patch) for ARM on Debian 7.4. I had some problems with cmake stuff, but not sure if this has to do with my configuration. It may be related, can you elaborate so I can confirm at my side? Do you have a test recipe for me to try? -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-qt5][PATCH] qmake5_base.bbclass: Use Qt version specific paths
On Wed, Feb 19, 2014 at 12:22:36AM -0300, Otavio Salvador wrote:
When looking for Qt5 components and files we ought to use the Qt5
specific path. In case the distribution wants to have a flat tree it
can set QT_DIR_NAME and it will still works as expected.
NAK
I don't think this is good idea, end-user applications shouldn't install
their data, archdata, examples etc in qt5 subdirectories.
https://github.com/meta-qt5/meta-qt5/wiki/Building-with-OE#wiki-bad-include-paths-and-build-failing-to-find-qt5-headers
If you don't care about qt4/qt5 separation just set empty QT_DIR_NAME
and all qtmodules will fold into default directories and you won't need
OE_QMAKE_PATH_HEADERS = ${OE_QMAKE_PATH_QT_HEADERS}
listed in above wiki.
Signed-off-by: Otavio Salvador ota...@ossystems.com.br
---
I have built two image and the SDK from scratch using this with no
issues. Could someone also give this a try?
classes/qmake5_base.bbclass | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/classes/qmake5_base.bbclass b/classes/qmake5_base.bbclass
index 3861cd0..ec0267a 100644
--- a/classes/qmake5_base.bbclass
+++ b/classes/qmake5_base.bbclass
@@ -57,20 +57,20 @@ do_generate_qt_config_file() {
cat ${QT_CONF_PATH} EOF
[Paths]
Prefix = ${OE_QMAKE_PATH_PREFIX}
-Headers = ${OE_QMAKE_PATH_HEADERS}
+Headers = ${OE_QMAKE_PATH_QT_HEADERS}
Libraries = ${OE_QMAKE_PATH_LIBS}
-ArchData = ${OE_QMAKE_PATH_ARCHDATA}
-Data = ${OE_QMAKE_PATH_DATA}
+ArchData = ${OE_QMAKE_PATH_QT_ARCHDATA}
+Data = ${OE_QMAKE_PATH_QT_DATA}
Binaries = ${OE_QMAKE_PATH_BINS}
LibraryExecutables = ${OE_QMAKE_PATH_LIBEXECS}
Plugins = ${OE_QMAKE_PATH_PLUGINS}
Imports = ${OE_QMAKE_PATH_IMPORTS}
Qml2Imports = ${OE_QMAKE_PATH_QML}
-Translations = ${OE_QMAKE_PATH_TRANSLATIONS}
-Documentation = ${OE_QMAKE_PATH_DOCS}
-Settings = ${OE_QMAKE_PATH_SETTINGS}
-Examples = ${OE_QMAKE_PATH_EXAMPLES}
-Tests = ${OE_QMAKE_PATH_TESTS}
+Translations = ${OE_QMAKE_PATH_QT_TRANSLATIONS}
+Documentation = ${OE_QMAKE_PATH_QT_DOCS}
+Settings = ${OE_QMAKE_PATH_QT_SETTINGS}
+Examples = ${OE_QMAKE_PATH_QT_EXAMPLES}
+Tests = ${OE_QMAKE_PATH_QT_TESTS}
HostBinaries = ${OE_QMAKE_PATH_HOST_BINS}
HostData = ${OE_QMAKE_PATH_HOST_DATA}
HostLibraries = ${OE_QMAKE_PATH_HOST_LIBS}
--
1.7.10.4
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-qt5][PATCH] qmake5_base.bbclass: Use Qt version specific paths
Martin,
On Thu, Feb 20, 2014 at 9:18 AM, Martin Jansa martin.ja...@gmail.com wrote:
On Wed, Feb 19, 2014 at 12:22:36AM -0300, Otavio Salvador wrote:
When looking for Qt5 components and files we ought to use the Qt5
specific path. In case the distribution wants to have a flat tree it
can set QT_DIR_NAME and it will still works as expected.
NAK
I don't think this is good idea, end-user applications shouldn't install
their data, archdata, examples etc in qt5 subdirectories.
https://github.com/meta-qt5/meta-qt5/wiki/Building-with-OE#wiki-bad-include-paths-and-build-failing-to-find-qt5-headers
If you don't care about qt4/qt5 separation just set empty QT_DIR_NAME
and all qtmodules will fold into default directories and you won't need
OE_QMAKE_PATH_HEADERS = ${OE_QMAKE_PATH_QT_HEADERS}
listed in above wiki.
and what about we change just the headers? I want to avoid every
recipe using Qt5 and qmake to require setting the headers var.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-qt5][PATCH] qmake5_base.bbclass: Use Qt version specific paths
Hello,
On Thu, Feb 20, 2014 at 9:22 AM, Otavio Salvador
ota...@ossystems.com.br wrote:
On Thu, Feb 20, 2014 at 9:18 AM, Martin Jansa martin.ja...@gmail.com wrote:
On Wed, Feb 19, 2014 at 12:22:36AM -0300, Otavio Salvador wrote:
When looking for Qt5 components and files we ought to use the Qt5
specific path. In case the distribution wants to have a flat tree it
can set QT_DIR_NAME and it will still works as expected.
NAK
I don't think this is good idea, end-user applications shouldn't install
their data, archdata, examples etc in qt5 subdirectories.
https://github.com/meta-qt5/meta-qt5/wiki/Building-with-OE#wiki-bad-include-paths-and-build-failing-to-find-qt5-headers
If you don't care about qt4/qt5 separation just set empty QT_DIR_NAME
and all qtmodules will fold into default directories and you won't need
OE_QMAKE_PATH_HEADERS = ${OE_QMAKE_PATH_QT_HEADERS}
listed in above wiki.
and what about we change just the headers? I want to avoid every
recipe using Qt5 and qmake to require setting the headers var.
Like this:
commit 0f8dc68b8bc8f129fbba4ee3692884f2324e9d28
Author: Otavio Salvador ota...@ossystems.com.br
Date: Tue Feb 18 14:03:49 2014 -0300
qmake5_base.bbclass: Use Qt version path for headers
When looking for Qt5 headers we ought to use the Qt5 specific path. In
case the distribution wants to have a flat tree it can set QT_DIR_NAME
and it will still works as expected.
Signed-off-by: Otavio Salvador ota...@ossystems.com.br
diff --git a/classes/qmake5_base.bbclass b/classes/qmake5_base.bbclass
index 3861cd0..0cfb5a4 100644
--- a/classes/qmake5_base.bbclass
+++ b/classes/qmake5_base.bbclass
@@ -57,7 +57,7 @@ do_generate_qt_config_file() {
cat ${QT_CONF_PATH} EOF
[Paths]
Prefix = ${OE_QMAKE_PATH_PREFIX}
-Headers = ${OE_QMAKE_PATH_HEADERS}
+Headers = ${OE_QMAKE_PATH_QT_HEADERS}
Libraries = ${OE_QMAKE_PATH_LIBS}
ArchData = ${OE_QMAKE_PATH_ARCHDATA}
Data = ${OE_QMAKE_PATH_DATA}
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-qt5][PATCH] qmake5_base.bbclass: Use Qt version specific paths
On Thu, Feb 20, 2014 at 09:22:03AM -0300, Otavio Salvador wrote:
Martin,
On Thu, Feb 20, 2014 at 9:18 AM, Martin Jansa martin.ja...@gmail.com wrote:
On Wed, Feb 19, 2014 at 12:22:36AM -0300, Otavio Salvador wrote:
When looking for Qt5 components and files we ought to use the Qt5
specific path. In case the distribution wants to have a flat tree it
can set QT_DIR_NAME and it will still works as expected.
NAK
I don't think this is good idea, end-user applications shouldn't install
their data, archdata, examples etc in qt5 subdirectories.
https://github.com/meta-qt5/meta-qt5/wiki/Building-with-OE#wiki-bad-include-paths-and-build-failing-to-find-qt5-headers
If you don't care about qt4/qt5 separation just set empty QT_DIR_NAME
and all qtmodules will fold into default directories and you won't need
OE_QMAKE_PATH_HEADERS = ${OE_QMAKE_PATH_QT_HEADERS}
listed in above wiki.
and what about we change just the headers? I want to avoid every
recipe using Qt5 and qmake to require setting the headers var.
That is still quite bad work around, because ideally end-user apps
shouldn't install headers in qt5 dirs as well.
So having this line explicitly in the recipe at least shows that app
headers will be installed in weird qt5 location (so your other recipes
should search for it there).
--
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-qt5][PATCH] qmake5_base.bbclass: Use Qt version specific paths
On Thu, Feb 20, 2014 at 9:42 AM, Martin Jansa martin.ja...@gmail.com wrote:
On Thu, Feb 20, 2014 at 09:22:03AM -0300, Otavio Salvador wrote:
Martin,
On Thu, Feb 20, 2014 at 9:18 AM, Martin Jansa martin.ja...@gmail.com wrote:
On Wed, Feb 19, 2014 at 12:22:36AM -0300, Otavio Salvador wrote:
When looking for Qt5 components and files we ought to use the Qt5
specific path. In case the distribution wants to have a flat tree it
can set QT_DIR_NAME and it will still works as expected.
NAK
I don't think this is good idea, end-user applications shouldn't install
their data, archdata, examples etc in qt5 subdirectories.
https://github.com/meta-qt5/meta-qt5/wiki/Building-with-OE#wiki-bad-include-paths-and-build-failing-to-find-qt5-headers
If you don't care about qt4/qt5 separation just set empty QT_DIR_NAME
and all qtmodules will fold into default directories and you won't need
OE_QMAKE_PATH_HEADERS = ${OE_QMAKE_PATH_QT_HEADERS}
listed in above wiki.
and what about we change just the headers? I want to avoid every
recipe using Qt5 and qmake to require setting the headers var.
That is still quite bad work around, because ideally end-user apps
shouldn't install headers in qt5 dirs as well.
So having this line explicitly in the recipe at least shows that app
headers will be installed in weird qt5 location (so your other recipes
should search for it there).
If a system is splitting Qt5 and Qt4 I don't think this is wrong. I
understand your point but I think this causes no harm for user and
easy the general usage.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] python-netifaces in oe?
On Thu, Feb 20, 2014 at 03:35:19PM +0100, Tobias Blom wrote: Hi Martin, Hi Tobias, I’m working with a yocto-project and needed a python module (netifaces). I now have a recipe for this, and I just wonder if it’s of any interest push this upstream? Better to ask in openembedded-devel@lists.openembedded.org Generally good recipes are always welcome. I’m pretty new to Yocto / OE, so I don’t really know how things works. Saw your name in the logs, and thought I’d just send an email and ask… By the way, thanks for your work! You're welcome -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com signature.asc Description: Digital signature ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-qt5][PATCHv2] nativesdk-qtbase: do qmake replacement in ${D} instead of ${B}
From: Denys Dmytriyenko de...@ti.com
* This way we don't mangle ${B} and can repeat do_install if necessary. And
previously it would require running do_compile again to restore the proper
state of ${B}.
* Need to bump PR, since do_compile isn't changing, but needs to re-run to
re-populate qmake-real binary.
Signed-off-by: Denys Dmytriyenko de...@ti.com
---
recipes-qt/qt5/nativesdk-qtbase.inc | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/recipes-qt/qt5/nativesdk-qtbase.inc
b/recipes-qt/qt5/nativesdk-qtbase.inc
index fa44009..3cb9b0e 100644
--- a/recipes-qt/qt5/nativesdk-qtbase.inc
+++ b/recipes-qt/qt5/nativesdk-qtbase.inc
@@ -10,6 +10,8 @@ require nativesdk-qt5.inc
# it's already included with newer oe-core, but include it here for dylan
FILESEXTRAPATHS =. ${FILE_DIRNAME}/qtbase:
+PR = r1
+
# common with -native and target version
SRC_URI += \
file://0001-Add-linux-oe-g-platform.patch \
@@ -192,14 +194,12 @@ do_install() {
# Fix install paths for all
find -name Makefile* | xargs sed -i
s,(INSTALL_ROOT)${STAGING_DIR_NATIVE}${STAGING_DIR_NATIVE},(INSTALL_ROOT)${STAGING_DIR_NATIVE},g
-# switch back the proper qmake
-if [ -e ${B}/bin/qmake-real ]; then
-rm ${B}/bin/qmake
-mv ${B}/bin/qmake-real ${B}/bin/qmake
-fi
-
oe_runmake install INSTALL_ROOT=${D}
+# replace the native qmake installed above with nativesdk version
+rm -rf ${D}${OE_QMAKE_PATH_HOST_BINS}/qmake
+install -m 755 ${B}/bin/qmake-real ${D}${OE_QMAKE_PATH_HOST_BINS}/qmake
+
# for modules which are still using syncqt and call
qtPrepareTool(QMAKE_SYNCQT, syncqt)
# e.g. qt3d, qtwayland
ln -sf syncqt.pl ${D}${OE_QMAKE_PATH_QT_BINS}/syncqt
--
1.8.3.2
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-qt5][PATCHv2] nativesdk-qtbase: do qmake replacement in ${D} instead of ${B}
Hello Denys,
On Thu, Feb 20, 2014 at 2:12 PM, Denys Dmytriyenko de...@denix.org wrote:
From: Denys Dmytriyenko de...@ti.com
* This way we don't mangle ${B} and can repeat do_install if necessary. And
previously it would require running do_compile again to restore the proper
state of ${B}.
* Need to bump PR, since do_compile isn't changing, but needs to re-run to
re-populate qmake-real binary.
Signed-off-by: Denys Dmytriyenko de...@ti.com
Works like a charm. I will wait until tomorrow to see if someone has
any extra feedback and push it.
Thanks for reworking the patch.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] GDM alternative?
Andreas, LXDM from meta-oe works well with minimal configuration on my part :) I didn't have to add another layer to satisfy dependencies. Thanks :) Adam On Wed, Feb 19, 2014 at 11:36 PM, Andreas Müller schnitzelt...@googlemail.com wrote: On Wed, Feb 19, 2014 at 5:15 PM, Adam Lee adam.yh@gmail.com wrote: Thank you Koen and Andreas. That has been really helped in clearing up my confusion and setting the path forward. I think I will try LXDM in meta-misc in meta-oe. Is there any special configuration that I should be aware of (other then setting it as the graphical init manager)? meta-misc is my personal playground - it might have dependencies to other layers and some things might not work as expected... Andreas ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] OEDAM: OpenEmbedded Developers (Americas) Meeting
The OpenEmbedded Project is holding a developers meeting May 2-3, 2014, in Santa Clara, CA. This meeting is immediately after the Embedded Linux Conference North America. All active OpenEmbedded and Yocto Project developers are invited to attend. NOTE: this is a development meeting for the project itself, not a training session. May 2-3, 2014 time TBD Ettus Research/National Instruments 4600 Patrick Henry Drive Santa Clara, CA 95054 USA Lunch will be provided on both days. For more information and to add yourself to the list of attendees, see the wiki page at http://openembedded.org/wiki/OEDAM Here are a couple of photos from 2009: http://www.flickr.com/photos/32615155@N00/sets/72157622653686647/ I'd like to thank Jefro for help with this announcement. Any errors are mine though. Philip, OpenEmbedded eV Chair. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-qt5][PATCH 1/2] qtbase.inc: configure with -openssl-linked instead of -openssl
Configure qtbase with -openssl-linked (instead of -openssl) to ensure
that run-time dependencies on libcryto and libssl are detected.
Signed-off-by: Andre McCurdy armccu...@gmail.com
---
recipes-qt/qt5/qtbase.inc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/recipes-qt/qt5/qtbase.inc b/recipes-qt/qt5/qtbase.inc
index f056393..ad5bb12 100644
--- a/recipes-qt/qt5/qtbase.inc
+++ b/recipes-qt/qt5/qtbase.inc
@@ -110,7 +110,8 @@ PACKAGECONFIG[kms] = -kms,-no-kms,kms
# needed for qtdeclarative (qtdeclarative.do_configure fails to find quick
module without)
PACKAGECONFIG[icu] = -icu,-no-icu,${ICU}
PACKAGECONFIG[udev] = -libudev,-no-libudev,udev
-PACKAGECONFIG[openssl] = -openssl,-no-openssl,openssl
+# use -openssl-linked here to ensure that RDEPENDS for libcrypto and libssl
are detected
+PACKAGECONFIG[openssl] = -openssl-linked,-no-openssl,openssl
PACKAGECONFIG[alsa] = -alsa,-no-alsa,alsa-lib
PACKAGECONFIG[pulseaudio] = -pulseaudio,-no-pulseaudio,pulseaudio
PACKAGECONFIG[nis] = -nis,-no-nis
--
1.8.1.2
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-qt5][PATCH 2/2] qtwebkit-examples: add missing RDEPENDS for ca-certificates
If qtbase is configured with openssl support (as it is by default)
then the qtwebkit example browser apps require CA certificates to
check the authenticity of https connections.
Signed-off-by: Andre McCurdy armccu...@gmail.com
---
recipes-qt/qt5/qtwebkit-examples.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-qt/qt5/qtwebkit-examples.inc
b/recipes-qt/qt5/qtwebkit-examples.inc
index 50c28cd..8a8e000 100644
--- a/recipes-qt/qt5/qtwebkit-examples.inc
+++ b/recipes-qt/qt5/qtwebkit-examples.inc
@@ -9,4 +9,4 @@ SRC_URI += \
DEPENDS += qtwebkit
-RDEPENDS_${PN}-examples += qtwebkit-qmlplugins
+RDEPENDS_${PN}-examples += qtwebkit-qmlplugins ca-certificates
--
1.8.1.2
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
