From: "Urs Fässler" <urs.fassler@bytesatwork.ch>
To: yocto@yoctoproject.org
Subject: Re: Headers missing in generated SDK
Date: Wed, 03 Dec 2014 14:20:52 +0100 [thread overview]
Message-ID: <547F0E34.2040206@bytesatwork.ch> (raw)
In-Reply-To: <CADuAu8RKxbAHrm2JaYErf3vTu7UnRmnqMAvhb9pzqo8EQ0+oaA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
Hi,
I added
TOOLCHAIN_TARGET_TASK += "my-super-package"
in the image recipe.
When I then populate the SDK against this image, I have my-super-package
in the SDK sysroot.
Regards
Urs
On 02.12.2014 20:45, Syed Moosvi wrote:
> Hi Matt,
>
> I added the following but still not getting headers in the
> generated SDK.
>
> *RDEPENDS_${PN}-dev = ""* # added to openssl bb file
>
> TOOLCHAIN_TARGET_TASK_append = " openssl-dev" # added to local.conf file
>
> Also, I don't get any errors when I don't add RDEPENDS_ but I think
> you were getting some errors.
> Any clues as to what I may be missing?
>
> Thanks,
>
> Syed
>
>
> On Wed, Nov 26, 2014 at 6:07 PM, Matt Schuckmann <Matt.Schuckmann@planar.com
>> wrote:
>
>> Syed,
>>
>> Your problem sounds similar to a problem I had getting my own headers and
>> static library included in the SDK.
>> Check out this thread to see if it helps.
>>
>> https://lists.yoctoproject.org/pipermail/yocto/2014-September/021678.html
>>
>> Matt S.
>>
>>
>
>
>
--
--
bytes at work
Technoparkstrasse 7
CH-8406 Winterthur
Switzerland
phone: +41 52 213 79 79
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-12-03 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 20:57 Headers missing in generated SDK Syed Moosvi
2014-11-26 18:07 ` Matt Schuckmann
2014-12-02 19:45 ` Syed Moosvi
2014-12-03 13:20 ` Urs Fässler [this message]
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=547F0E34.2040206@bytesatwork.ch \
--to=urs.fassler@bytesatwork.ch \
--cc=yocto@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.