From 49f2a0192d0d0db65f6dd44eabdbdd4ee2886bac Mon Sep 17 00:00:00 2001 From: Samuli Piippo Date: Wed, 13 Jan 2016 10:07:13 +0200 Subject: qtbase: use PACKAGECONFIG to ensure runtime dependency to libssl Using openssl-linked configure has side effect that gdb catches the SIGILL signal, which openssl uses internally on ARM, every time when starting debugging any Qt application. This is annoying and somewhat confusing behavior even with QtCreator. Using the default openssl configure argument prevents this, while using the 4th argument for PACKAGECONFIG keeps the runtime dependency to libssl correctly in place. Change-Id: I3eb33ffc08980565930169710ed81de5fd4e0aa8 Reviewed-by: Teemu Holappa --- recipes-qt/qt5/qtbase_git.bbappend | 3 +++ 1 file changed, 3 insertions(+) (limited to 'recipes-qt') diff --git a/recipes-qt/qt5/qtbase_git.bbappend b/recipes-qt/qt5/qtbase_git.bbappend index 3db4e07..4e9057a 100644 --- a/recipes-qt/qt5/qtbase_git.bbappend +++ b/recipes-qt/qt5/qtbase_git.bbappend @@ -46,3 +46,6 @@ do_configure_prepend() { } SRCREV = "3880f41e683f02b905c8cbc3c578c3f3a0a1eb2e" + +# Temporarily here, until merged upstream +PACKAGECONFIG[openssl] = "-openssl,-no-openssl,openssl,libssl" -- cgit v1.2.3-54-g00ecf