Hi, thanks for reply and sorry, been busy with other stuff.
Regarding esdk - what is their purpose now, when there is this new workflow? I
mean, in what use cases would you use esdk instead of this new workflow?
For example, i'm now trying to setup ci/cd pipeline for testing using qemu. Is
it g
Hi Alex, Adrian,
thanks for the explanation. I checked the slides, watched the video and tried
this workflow (partially - didn't try deploy-target and finish), and it seems
to work, but still have some questions:
* Alex, you write above: Classic esdk bundles will almost certainly not be
develop
Hi Alex,
thank you for the prompt reply. As for me personally, I am, actually, using the
yocto environment, as the yocto maintainer within our project, but wanted to
create esdk for the developers as i hoped it would be easier for them to work
with recipes and for me/us to maintain it all toget
Hello,
I'm trying to do the following (after generating and installing my esdk and
sourcing the environment script):
* devtool modify recipe
* do some coding and testing
* devtool finish recipe meta-custom -m srcrev
I want just to update SRCREV of the recipe, *not* to create source code patches
