colleague asked what should have been an easy question, but as i've
never spent a lot of time digging into the intricacies of generating
SDKs (i guess i will now), i didn't have an immediate answer.
current SDK manual in section 3 regarding standard SDKs states
that, "The Standard SDK provides a cross-development toolchain and
libraries tailored to the contents of a specific image." ok, saying
the SDK is tailored to the contents of a specific image makes sense if
one generates the SDK by selecting a particular image, say:
$ bitbake -c populate_sdk core-image-minimal
$ bitbake -c populate_sdk core-image-sato
in those cases, one is identifying an image to use as the basis for
the generated SDK, and i'm assuming that those image definitions can
affect the final SDK generation by, perhaps, defining
TOOLCHAIN_HOST_TASK and TOOLCHAIN_TARGET_TASK and so on.
however, one can also generate a standard SDK with the generic
(image-independent):
$ bitbake meta-toolchain
which clearly does not identify an image (all that recipe does,
really, is "inherit populate_sdk"), so i *guessed* that using that
command will generate a standard SDK based only on what can be found
in the various .conf files and associated variables (MACHINE, DISTRO,
etc.) without being tied to a particular image.
just about to dive into the details, but is the above at least a
simplistic way of looking at it?
rday
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#49862): https://lists.yoctoproject.org/g/yocto/message/49862
Mute This Topic: https://lists.yoctoproject.org/mt/75311311/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
