RE: [PATCH] sdk: make SDK and image

["Schmidt, Adriaan" <adriaan.schmidt@siemens.com>]

Kiszka, Jan (T RDA IOT), 15. Dezember 2021 08:52:
> On 15.12.21 07:41, Adriaan Schmidt wrote:
> > This derives the SDK from image.bbclass (currently it only
> > inherits rootfs), removing the awkward and custom tar-xz'ing.
> > Note that because there is not tarxz-img IMAGE_TYPE, we switch
> > the SDK type to targz-img. This is only temporary, until we have
> > the OE-inspired imagetypes.
> >
> > API change: SDK is now no longer built using `bitbake my_image
> >     -cpopulate_sdk`, but using `bitbake isar-sdk`. We could of course
> >     keep the old commands working, but I could not find any
> >     connection between the target image and the contents of the SDK
> >     (while building the SDK using the target image recipe confusingly
> >     makes it look like there is such a connection).
> 
> This is not correct: The target image recipe may define SDK_[PRE]INSTALL
> in correspondance to its content. Also, changing the user API would
> needlessly break the alignment with OE.

But the SDK is built by a completely different recipe (sdkchroot, inheriting rootfs), so how does SDK_[PRE]INSTALL set in the target image recipe have any effect there? Looks to me that those variables need to be set in some .conf for this to work, but maybe I'm missing something...

Adriaan