Yocto, native and nativesdk
---------------------------

For native only recipes, it is probably more convenient to go for the
foobar-native.bb alternative.

As explicitly mentioned in the documentation, if a recipe is
nativesdk, the conventional filename is not "foobar-native.bb" but
"nativesdk-foobar.bb".  Not very consistent, but so it is.

A nativesdk package "foo" might have dependencies towards a package "bar".
Should "nativesdk-foo.bb" depend on "bar-nativesdk" or "bar-native"?
The answer is: go for "bar-native".

Anecdotal report: I've recently defined a recipe for "foo-nativesdk",
that depends on a "bar" recipe.  The compilation of "foo" requires an
executable to generate the code, and the executable is provided by
"bar".  Depending on bar-nativesdk ended up failing because the
executable could not be invoked.  The failure was due to the dynamic
linking interpreter ld.so(8) being missing.
The executable installed by bar-nativesdk was referring to a missing
loader, pointing to a position in the filesystem where it would have
been positioned by the SDK setup.