From: William Mills <wmills@ti.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: poky@yoctoproject.org
Subject: Re: Qt should be linked to openssl at compilation
Date: Wed, 16 Nov 2011 16:57:00 -0500 [thread overview]
Message-ID: <4EC431AC.2010207@ti.com> (raw)
In-Reply-To: <4EC42C07.7010409@windriver.com>
On 11/16/2011 04:32 PM, Mark Hatle wrote:
> On 11/16/11 3:20 PM, Francois Dupoux wrote:
>> ----- Original Message -----
>> From: "Mark Hatle"<mark.hatle@windriver.com>
>> To: poky@yoctoproject.org
>> Sent: Wednesday, 16 November, 2011 8:57:14 PM
>> Subject: Re: [poky] Qt should be linked to openssl at compilation
>>
>>> So it would be great to just link Qt with openssl so that all SSL
>>> related classes can work.
>>>
>>> We just need to add "-openssl-linked" to QT_CONFIG_FLAGS in
>>> recipes-qt/qt4.
>>
>> Slightly off topic perhaps, but are you using the RPM packaging
>> back-end?
>>
>> This should have identified the usage of the openssl library and
>> added it to the
>> dependency set. If it didn't I'm interested to know why it failed to
>> detect it.
>>
>> This is an outstanding enhancement request to add that same level of
>> dependency
>> detection to deb and ipkg. Until then, if you want to use deb or
>> ipkg you will
>> likely need to add an RDEPENDS to openssl to get the dynamic version.
>>
>> Hi Mark,
>>
>> Yes, I am using RPM packages, with the latest stable version (poky-6.0)
Francois, are you building your application using bitbake or
externally? Are you adding it to your board using an RPM package or
just coping it there?
If your building it externally and just copying it, all the magic others
are talking about won't happen. However you can just add the openssl
packages to you target. You can do this by building them and using RPM
or you can create a custom image/task recipie and add the needed
packages. You could even use HOB if you want an easy way to create a
custom image.
If your building your app in bitbake, then ignore me and continue your
conversation with Mark.
next prev parent reply other threads:[~2011-11-16 21:57 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 [this message]
2011-11-16 22:33 ` Francois Dupoux
2011-11-16 22:09 ` Holger Hans Peter Freyther
2011-11-16 23:42 ` Mark Hatle
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=4EC431AC.2010207@ti.com \
--to=wmills@ti.com \
--cc=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.