clarifying issues building two SDKs, based on different target images

["Robert P. J. Day" <rpjday@crashcourse.ca>]

  if you can tolerate it, a few more questions about building SDKs
before i sit down and start burning through machine cycles configuring
and building for the rest of the day.

  first, given that:

"SDK_RDEPENDS=${TOOLCHAIN_TARGET_TASK} ${TOOLCHAIN_HOST_TASK}"

do those two variables map *precisely* to the target.manifest and
host.manifest files generated when building an SDK? they *appear* to,
i just wanted to ensure there wasn't some subtle mismatch that might
confuse me later.

  next, i assume that if, in the same build directory, i choose to
build two standard SDKs differing in only the target image:

$ bitbake -c populate_sdk core-image-minimal
$ bitbake -c populate_sdk core-image-sato

all common files between the two SDKs will be reused in the final
construction. so if i build an SDK based on core-image-sato, turning
around and building one based on core-image-minimal should take very
little time indeed, correct?

  finally (and the one i'm most unsure about), if i build those two
SDKs, i'm *assuming* that the x86 nativesdk content will be the same;
it's the target PPC sysroots that will be different (obviously, the
sysroot for sato will be noticeably larger than the one for minimal).

  what happens if i try to install those two SDKs in the same
directory (/opt/poky.2.2/)? would that even work?

  and now, off to read more manual ...

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================