From: Khem Raj <raj.khem@gmail.com>
To: Navani Srivastava <navani.srivastava@gmail.com>,
Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
Navani Srivastava <navani.srivastava@lnttechservices.com>
Subject: Re: Integration of custom recipe with SDK
Date: Thu, 25 Sep 2014 20:23:22 -0700 [thread overview]
Message-ID: <5424DC2A.1060002@gmail.com> (raw)
In-Reply-To: <CA+Z6RkUk5zeR3SiYd_ce2cY0-9fDSErhZuO4h2h9V-2ckp9icQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 9/24/14 5:01 AM, Navani Srivastava wrote:
> Removing integration of meta-toolchain-qte from my image helped in building
> qjson as a part of SDK when running bitbake -c populate_sdk -v <myimage> or
> bitbake <myimage>.
>
OK. Thats what is expected.
> Integration of meta-toolchain-qte might need some more modifications.
>
> Still as a requirement, I need to integrate my custom recipe with
> meta-toolchain-qte to generate SDK having custom recipe as a tool.
when populate_sdk gives you an SDK I dont understand why this is a
requirement
I have
> created nativesdk bb file for custom recipe to integrate it via
> nativesdk-packagegroup-qte-toolchain-host.bb but no luck..
>
> On Wed, Sep 24, 2014 at 1:14 PM, Navani Srivastava <
> navani.srivastava@gmail.com> wrote:
>
>> Yes.. i did...
>> On 24 Sep 2014 12:56, "Paul Eggleton" <paul.eggleton@linux.intel.com>
>> wrote:
>>
>>> On Wednesday 24 September 2014 10:26:41 Navani Srivastava wrote:
>>>> I corrected FILES_${PN} and added following in my image recipe-
>>>> QTNAME = "qte"
>>>> QT_DIR_NAME = "qtopia"
>>>> require recipes-qt/meta/meta-toolchain-qt.bb
>>>>
>>>> but that didn't make any difference related to SDK integration. On
>>>> executing 'bitbake -v <MyImageName>', it is generating rootfs and sdk,
>>> in
>>>> which contains rootfs contains qjson libraries but sdk doesn't integrate
>>>> anything.
>>>
>>> To generate the SDK you'd need to also do bitbake -c populate_sdk
>>> <imagename>
>>> - you did do that as well after making the changes to the recipe, right ?
>>>
>>> Cheers,
>>> Paul
>>>
>>> --
>>>
>>> Paul Eggleton
>>> Intel Open Source Technology Centre
>>>
>>
>
- --
- -Khem
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org
iEYEARECAAYFAlQk3CoACgkQuwUzVZGdMxS3EgCfVUdFehr4kmLrXfLy6jN25Q0e
YSAAn3Dhe/y2xVpFYtpTtDMGCA7qOQR5
=FZTr
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-09-26 3:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 12:12 Integration of custom recipe with SDK Navani Srivastava
2014-09-18 20:32 ` Randy Witt
2014-09-20 23:05 ` Khem Raj
2014-09-21 3:56 ` Navani Srivastava
2014-09-22 8:15 ` Paul Eggleton
2014-09-22 8:36 ` Navani Srivastava
2014-09-22 8:51 ` Paul Eggleton
2014-09-22 9:18 ` Navani Srivastava
2014-09-23 4:26 ` Navani Srivastava
2014-09-23 5:54 ` Khem Raj
2014-09-24 4:56 ` Navani Srivastava
2014-09-24 7:26 ` Paul Eggleton
2014-09-24 7:44 ` Navani Srivastava
2014-09-24 12:01 ` Navani Srivastava
2014-09-26 3:23 ` Khem Raj [this message]
2014-10-08 9:42 ` Navani Srivastava
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=5424DC2A.1060002@gmail.com \
--to=raj.khem@gmail.com \
--cc=navani.srivastava@gmail.com \
--cc=navani.srivastava@lnttechservices.com \
--cc=paul.eggleton@linux.intel.com \
--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.