Currently we support installing extra target packages (and their headers) into an SDK sysroot to enable the developer to customise their SDK environment. However the SDK only ships with opkg package manager support whereas we build RPM target packages by default. I'd propose we need to spend some time thinking about the workflow for a developer extending their SDK and how best to support it then ensure that said workflow is well documented.
This is a valid enhancement. Workflow will be addressed in the "to-be-written" Yocto Project Development manual. This manual is where this topic should be addressed. This enhancement will be implemented post 1.0.
Hi Lianhao, This is something related to package feed which I though at one point you looked into. So have we provided Scott the needed info to document them? Thanks, Jessica
I don't currently have information for this. I will need to work with someone that is the Subject Matter Expert on this. Scott
I am changing this to NEEDINFO as that is what I need. I don't have any base information to address this issue yet. Scott
Jessica: Can you please either provide Scott with info, or find someone who can?
Hi Scott, I see there are some related sections about SDK across the dev manual, ref manual and adt manual. Could you please tell me what kind of information is still needed? Best Regards, Chen Qi
I'm marking this as obsolete - we have a plan to handle this as part of the developer workflow improvements (see bug 6662).