colleague just asked me about the difference between building an SDK with either of:
$ bitbake meta-toolchain $ bitbake -c populate_sdk <some target> i know that the meta-toolchain recipe file contains little more than inheriting populate_sdk so, without checking, i speculated wildly as follows: "bitbake meta-toolchain" takes no target, so it's limited to whatever info it can glean from local.conf and bitbake.conf and so on and so on, things like MACHINE and DISTRO, and whatever assignments to TOOLCHAIN_HOST_TASK, etc, it runs into in its travels; in essence, it's a "generic" toolchain. on the other hand, "bitbake -c populate_sdk <target>" can, in addition, consult the target recipe file where it can collect even further SDK defining info, like what you find in core-image-sato.bb: TOOLCHAIN_HOST_TASK_append = " nativesdk-intltool nativesdk-glib-2.0" at the risk of over-simplification, is that a not wholly inaccurate explanation of the difference? rday
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#149679): https://lists.openembedded.org/g/openembedded-core/message/149679 Mute This Topic: https://lists.openembedded.org/mt/81456418/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
