To be honest, I'm not entirely sure what the uninative stuff is (explanations
or pointers to explanations appreciated!) but I'm trying to figure out how to
work with it.
Previously, generating an eSDK didn't require a uninative-tarball, but now,
apparently, it does? Any idea why?
So now, in addition to building the uninative-tarball before being able to
build an eSDK, it also appears that I have to edit my local.conf to tell the
build that I'm using it, where to find it, and its md5sum. The weird thing is,
I could do "bitbake uninative-tarball" all day long, and every invocation of
that command will generate a tarball with a different md5sum even though the
configuration for each build is exactly the same!