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

[Khem Raj]

> On Oct 22, 2016, at 9:05 AM, Robert P. J. Day <rpjday at crashcourse.ca> wrote:
> 
> 
>  i'm about to dive into SDKs seriously for the first time, so a
> shamefully dumb question to make sure i'm starting with the correct
> understanding.
> 
>  starting with up-to-date OE master branch, i selected
> 
> MACHINE=mpc8315e-rdb
> 
> now, as i see it, i can create just the SDK with either of:
> 
> $ bitbake meta-toolchain
> $ bitbake -s populate_sdk core-image-minimal
> 
> (in that second command, i'm assuming the choice of image is
> irrelevant, i just always use core-image-minimal out of habit.)
> 
>  i'm assuming those commands are entirely equivalent in terms f
> generating the SDK, given that meta-toolchain.bb consists solely of:
> 
>  SUMMARY = "Meta package for building a installable toolchain"
>  LICENSE = "MIT"
> 
>  PR = "r7"
> 
>  LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
> file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
> 
>  inherit populate_sdk
> 
> so the more efficient of those commands would be just
> 
> $ bitbake meta-toolchain
> 
>  also, i did notice the generated host.manifest and target.manifest
> files created along with the SDK -- am i correct in assuming those
> files represent, respectively, the TOOLCHAIN_HOST_TASK and
> TOOLCHAIN_TARGET_TASK values?
> 
>  anyway, as long as i'm starting with the right info, pretty sure i
> can take it from there, accompanied by the SDK manual:
> 
> http://www.yoctoproject.org/docs/2.2/sdk-manual/sdk-manual.html


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

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

Thanks
-Khem
-------------- 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/f789cad8/attachment-0002.sig>