[yocto] Working on Dependent Recipes in eSDK

[Khem Raj]

On Thu, Oct 25, 2018 at 8:29 AM <Aaron_Wright at selinc.com> wrote:
>
> > ChenQi <Qi.Chen at windriver.com> wrote on 10/22/2018 07:04:32 PM:
> >
> > Hi Aaron,
> >
> > The main pain for now is that `devtool sdk-install <DEPEND_RECIPE>' does
>
> > not work as expected, right?
> > I just checked the codes of sdk-install, and found that it does not fit
> > the current RSS design.
> > I'd like to check with you if this is the major concern from your team?
> > Do you have some other concerns?
> > I'll open enhancements/bugs on bugzilla and hopefully will work on them
> > in the 2.7 development cycle.
> >
> > Best Regards,
> > Chen Qi
> >
> > ... snip ...
>
> Well, I'm not quite sure how "devtool sdk-install <DEPENDENT_RECIPE>"
> relates after "devtool modify <DEPENDENT_RECIPE>" has been called.
>
> My developers use devtool to install dependent recipes into the eSDK when
> they start working on something. Often they find that they need to make a
> change in the library code that a dependent recipe provides. In effect,
> they are developing a patch for the dependent recipe. So they use devtool
> to say they're going to modify that dependent recipe, and they go and
> make the changes they want. Then what? How do they get those changes,
> that patch, available to the eSDK?
>
> Any changes made to the library code provided by the dependent recipe are
> not available to the eSDK, except through devtool commands. In effect
> there are two different worlds at play, the eSDK sysroots versus the
> recipe sysroots. The devtool commands seem to make use of the recipe
> sysroots, but in my mind that defeats the purpose of an eSDK. So I made
> a plug-in for devtool were I can force the eSDK sysroots to be updated.
> I'm not sure how that works, but it seems to propagate the workspace
> (recipe sysroot land) to the eSDK, so changes that developers make are
> now available for use.
>
> I want my developers to use the toolchain (cmake, make, gcc, etc)
> provided by the eSDK and by things installed into it
> (devtool sdk-install), rather than having to use devtool as their
> iterative build command.
>
> Ultimately, I would like to be able to skip my devtool plug-in, as it
> requires the use of "devtool build <DEPENDENT_RECIPE>" and
> "devtool sdk-sysroot" each time a dependent recipe is modified. But I am
> not sure how that would work, other than the devtool build command
> should be updating the eSDK sysroots itself.

I think you have two options here

1. Feedback the tweaks to packages back into source and re-generate
SDK and if you setup SDK feeds then users/devs can simply do
devtool sdk-update
and this time the package in question will get updated in their SDKs
with the change that was initiated.

second option could be to generate a downstream derivative SDK using
devtool build-sdk and use this SDK


> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto