On Mon, 30 Sept 2024 at 14:33, Radoslav Pesek via
Lists.Yoctoproject.Org
wrote:
> 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?
There is no purpose, other than compatibility with legacy pr
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
On Mon, 9 Sept 2024 at 16:24, Radoslav Pesek via
lists.yoctoproject.org
wrote:
> 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 w
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
On Sun, 2024-09-08 at 15:46 +0200, Alexander Kanavin wrote:
> On Sun, 8 Sept 2024 at 15:24, Adrian Freihofer
> wrote:
> > It is true that we have replaced our eSDK-based setups with Direct
> > SDK-
> > based setups. A year ago, I had the opportunity to talk about this
> > topic at Yocto Sumit: fil
On Sun, 8 Sept 2024 at 15:24, Adrian Freihofer
wrote:
> It is true that we have replaced our eSDK-based setups with Direct SDK-
> based setups. A year ago, I had the opportunity to talk about this
> topic at Yocto Sumit: file:///home/adrian/Downloads/yocto-summit-
> 2023.11-devtool-i_S04eDYy.pdf
>
On Sat, 2024-09-07 at 12:41 +0200, Alexander Kanavin wrote:
> On Fri, 6 Sept 2024 at 15:54, Radoslav Pesek via
> Lists.Yoctoproject.Org
> wrote:
> > thank you for the prompt reply. As for me personally, I am,
> > actually, using the yocto environment, as the yocto maintainer
> > within our project
On Fri, 6 Sept 2024 at 15:54, Radoslav Pesek via
Lists.Yoctoproject.Org
wrote:
> 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
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
Unfortunately when standalone esdk archives are made, the layers are
copied into the archive with a simple file tree operation, and all git
history and pointers to upstream repos are thrown away.
I would recommend setting up a plain, direct yocto environment
instead. There's an officially supporte
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
11 matches
Mail list logo
