[OE-core] basic bitbake commands to create an SDK?

Khem Raj raj.khem at gmail.com
Sat Oct 22 16:55:56 UTC 2016


> On Oct 22, 2016, at 9:53 AM, Robert P. J. Day <rpjday at crashcourse.ca> wrote:
> 
> On Sat, 22 Oct 2016, Khem Raj wrote:
> 
>> generally meta-toolchain is prior art. You want to use image
>> specific SDKs so -cpopulate_sdk <image> is fine. In this case it
>> will include the needed dev headers/libs in your SDK for that given
>> image automatically it can be any image
> 
>  ah, good to know, i was starting to get that impression from the
> readings. (is there any mention in the docs that meta-toolchain is
> deprecated? if that's the correct word.)
> 
>> I would recommend to try using eSDK, which can be generated using
>> -cpopulate_sdk_ext see
>> 
>> https://wiki.yoctoproject.org/wiki/Application_Development_with_Extensible_SDK
> 
>  i was just perusing the testsdk.bbclass file, where i read at the
> top:
> 
>  # testsdk.bbclass enables testing for SDK and Extensible SDK
>  #
>  # For run SDK tests you need to do,
>  # - bitbake core-image-sato -c populate_sdk
>  # - bitbake core-image-sato -c testsdk
>  #
>  # For run eSDK tests you need to do,
>  # - bitbake core-image-sato -c populate_sdk_ext
>  # - bitbake core-image-sato -c testsdkext
> 
> does that testing actually require the core-image-sato image? that's
> certainly what those comments seem to suggest.

it should work with any image.

> 
> rday
> 
> --
> 
> ========================================================================
> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>                        http://crashcourse.ca
> 
> Twitter:                                       http://twitter.com/rpjday
> LinkedIn:                               http://ca.linkedin.com/in/rpjday
> ========================================================================
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20161022/5d894f67/attachment-0002.sig>


More information about the Openembedded-core mailing list