Tool/software:
im used to yocto sdk being part of the target build.
example:
bitbake <my_custom_content_image> -c populate_sdk
but what TI is doing:
bitbake meta-toolchain-arago-tisdk
No image defined?
since there is no reference to the target I'm building for my sdk i keep having missing components. ie sdk is not including needed content.
we need to build multiple outputs for various reasons which is why all our included components for various image builds are in a custom target layer bb file and not just hardcoded in local.conf.
how do you get this original yocto behavior back when its this one off sdk command (bitbake meta-toolchain-arago-tisdk)?
its not following specified target which always had automatically include packages by its nature?
can we get standard bitbake <my_custom_content_image> -c populate_sdk to work like it should?
or a workaround to make it always include the target image we need to generate the sdk for? again this cant just be a flat local.conf that kills custom target outputs.
we have a lot of automation and source control wrapped around yocto to make it scriptable to pull and generate. so changes needs to all exist within our custom meta-layer and not mess with other meta layers folders we dont own and control.
it was always strait forward when its original yocto behavior to generate sdk via -c populate_sdk.
Now im a little confused how this is supposed to work thus my forum hail marry.