On Thu, Oct 25, 2018 at 8:29 AM wrote:
>
> > ChenQi wrote on 10/22/2018 07:04:32 PM:
> >
> > Hi Aaron,
> >
> > The main pain for now is that `devtool sdk-install ' does
>
> > not work as expected, right?
> > I just checked the codes of sdk-install, and found that it does not fit
> > the current R
> ChenQi wrote on 10/22/2018 07:04:32 PM:
>
> Hi Aaron,
>
> The main pain for now is that `devtool sdk-install ' 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
Hi Aaron,
The main pain for now is that `devtool sdk-install ' 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 concer
> Paul Eggleton wrote on 10/18/2018
12:30:07 PM:
>
> I think we would *like* this to be possible, from what I can tell I
think the
> issue is that the copies of the library in the sysroots of other
dependent
> recipes aren't being updated. The eSDK (and devtool) were originally
written
> wh
> Alexander Kanavin wrote on 10/18/2018 11:30:17
AM:
>
> I don’t think esdk is designed for this kind of ‘full stack’
> development. You can go back to working directly with yocto layers,
> and skip the esdk altogether. Devtool will work exactly same (minus
> the sdk specific commands).
>
> A
I think we would *like* this to be possible, from what I can tell I think the
issue is that the copies of the library in the sysroots of other dependent
recipes aren't being updated. The eSDK (and devtool) were originally written
when there weren't recipe-specific sysroots, and this stuff was a
I don’t think esdk is designed for this kind of ‘full stack’ development. You
can go back to working directly with yocto layers, and skip the esdk
altogether. Devtool will work exactly same (minus the sdk specific commands).
Alex
> On 18 Oct 2018, at 19.37, aaron_wri...@selinc.com wrote:
>
> M
My team recently started using the eSDK for day-to-day development.
Previously, they were using the bitbake command to build, which works, but
has overhead. Yesterday three different people came up to me a question
about workflow with the eSDK, and they all had to do with dependent
recipes in t
