From: Mark Hatle <mark.hatle@windriver.com>
To: <poky@yoctoproject.org>
Subject: Re: Qt should be linked to openssl at compilation
Date: Wed, 16 Nov 2011 17:42:22 -0600 [thread overview]
Message-ID: <4EC44A5E.2050206@windriver.com> (raw)
In-Reply-To: <4EC4348B.7010003@freyther.de>
On 11/16/11 4:09 PM, Holger Hans Peter Freyther wrote:
> On 11/16/2011 10:32 PM, Mark Hatle wrote:
>
>>
>> I'd like to try to reproduce this linking to openssl, but not getting
>> referenced in the dependency set.
>
> Qt has three SSL options:
> 1.) no SSL
> 2.) dlopen at runtime (the one probably configured), some people
> believe it avoids the OpenSSL advertizement clause.. and saves
> static initialization when SSL is not used..
Ahh, I didn't know there was a dlopen option. If that is the case then there is
no way for auto detection to be able to determine the need for OpenSSL. So
RDEPENDS would be the correct way in that case.
--Mark
> 3.) link to OpenSSL (the -openssl-linked config option the original
> mail is referring to)
>
>
> Either you do 2.) and make QtNetwork RDEPEND on libssl/libcrypt and make sure
> the symlinks are present... or you do 3.) as proposed in the original email.
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
next prev parent reply other threads:[~2011-11-16 23:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <37aa3d7e-7cbb-48f7-8339-8f2b6f7ee06d@zimbra33-e6.priv.proxad.net>
2011-11-16 19:47 ` Qt should be linked to openssl at compilation Francois Dupoux
2011-11-16 20:38 ` Holger Hans Peter Freyther
2011-11-16 20:57 ` Mark Hatle
2011-11-16 21:20 ` Francois Dupoux
2011-11-16 21:32 ` Mark Hatle
2011-11-16 21:57 ` William Mills
2011-11-16 22:33 ` Francois Dupoux
2011-11-16 22:09 ` Holger Hans Peter Freyther
2011-11-16 23:42 ` Mark Hatle [this message]
2011-11-16 22:30 ` Francois Dupoux
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=4EC44A5E.2050206@windriver.com \
--to=mark.hatle@windriver.com \
--cc=poky@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.