Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt 5.0.2 with OpenSSL
Date: Tue, 8 Oct 2013 10:48:58 +0200	[thread overview]
Message-ID: <20131008104858.69c60676@skate> (raw)
In-Reply-To: <CA+csPL7n8=fX7LLyLE4uS4s4uXHTYoLyNVm66b6_Dj0k3N+p-Q@mail.gmail.com>

Dear Espen Frimann Koren,

On Tue, 8 Oct 2013 10:43:17 +0200, Espen Frimann Koren wrote:

> When both BR2_PACKAGE_QT5BASE_NETWORK and BR2_PACKAGE_OPENSSL are set,
> something fails in the linking of libQt5Network.so that is related to
> OpenSSL.

Do you have the exact error message?

> I do not have time to figure out why, but suggest the
> following change so that you do not have to compile Qt with OpenSSL
> support even if you include OpenSSL in your build:
> 
> In package/qt5/qt5base/Config.in:
> 
> if BR2_PACKAGE_QT5BASE_NETWORK
> config BR2_PACKAGE_QT5BASE_OPENSSL
>   bool "use openssl"
>   depends on BR2_PACKAGE_OPENSSL
>   default BR2_PACKAGE_OPENSSL
>   help
>     This option toggles use of OpenSSL in Qt5
> 
> And in package/qt5/qt5base/qt5base.mk:
> Change BR2_PACKAGE_OPENSSL to BR2_PACKAGE_QT5BASE_OPENSSL (around
> lines 113 and 114)

Right, but for OpenSSL support, we generally want it to be enabled
automatically when the OpenSSL package is selected. The current
implementation is in fact a "feature", and the real fix is to
understand what build failure you're getting and make sure Qt5 can link
properly against OpenSSL.

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-10-08  8:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08  8:43 [Buildroot] Qt 5.0.2 with OpenSSL Espen Frimann Koren
2013-10-08  8:48 ` Thomas Petazzoni [this message]
     [not found]   ` <CA+csPL5q=rYc_-Q4enRD07Pomj9A6hossAB9cesFnMNnLQv5GA@mail.gmail.com>
2013-10-09  7:51     ` Thomas Petazzoni
2013-10-09  8:23       ` Espen Frimann Koren
2013-10-09  8:58         ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131008104858.69c60676@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox