Defining the content of the SDK

[Jan Kiszka <jan.kiszka@siemens.com>]

Hi all,

we are just looking more closely at the SDK Isar can generate, and that in the 
context of a concrete target. It quickly became clear that we miss a lot of 
packages and also configurability.

Currently, there is a hard-coded SDKCHROOT_PREINSTALL that defines which 
additional packages, besides the core toolchain, should go into the SDK. 
However, if you have libfoo on your target, you possibly want libfoo-dev in your 
SDK in order to develop against that.

Now the question is if it could be sufficient to derive the required -dev 
packages from the target image or if we should rather or additionally allow to 
augment the installed package set. Is there any simple pattern we can inherit 
from OE?

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux