[OE-core] SDK confusion!

[Bjørn Forsman]

Hi Mark,

On 17 December 2012 16:40, Mark Hatle <mark.hatle at windriver.com> wrote:
> On 12/17/12 9:31 AM, Bjørn Forsman wrote:
>> Hi,
>>
>> I'm really confused about how to use/customize the generated SDK in
>> openembedded. I've spent two days messing around with angstrom
>> setup-scripts, poky and yocto and now I really need help.
[...]
> In oe-core with the branch tag 'denzil' or the master, there are two ways of
> generating an SDK.
>
> The first (which is also present in the older oe-core systems) uses a
> specific SDK recipe.  For instance, meta-toolchain.  This recipe simply
> makes the toolchain elements available to you and you need to provide the
> necessary sysroot for your SDK.  An alternative is something like
> meta-toolchain-gmae which provides a specific set of sysroot components for
> the 'gnome mobile applicable environment.'
>
> The advantage of this first way is it allows a product designer to release a
> targeted SDK for their application developers.  You don't have to put
> everything that will end up on the target image into the SDK, only the
> libraries, headers and interfaces that an app developer are allowed to use.
>
> The second way (which is newer) is the ability to generate an SDK based on
> the contents of the image.  This uses a new task called "populate_sdk" that
> can be run with any image recipe, i.e. "bitbake core-image-minimal -c
> populate_sdk". This will generate an SDK image that includes the software
> from the image, in addition to related -dev and -dbg packages.
>
> The advantage of this second way is that you have an SDK that enables
> developing for the contents of the image, as well as system wide
> cross-debugging with the -dbg packages.
>
> The items below are specific to one packaging system, opkg.  The items above
> are generic and are expected to work in any of the supported methods.

Thank you very much!

"bitbake <image-name> -c populate_sdk" is exactly what I want. Brilliant!

Best regards,
Bjørn Forsman