> -----Original Message----- > From: Burton, Ross <ross.bur...@intel.com> > Sent: Friday, January 4, 2019 4:12 AM > To: Edmund Nadolski <edmund.nadol...@microsoft.com> > Cc: Yocto-mailing-list <yocto@yoctoproject.org> > Subject: Re: [yocto] Yocto staged builds? > > On Fri, 21 Dec 2018 at 01:19, Edmund Nadolski > <edmund.nadol...@microsoft.com> wrote: > > > Yocto is generally flexible enough that any signing that isn't > > > currently doesn't wouldn't be too difficult to add. > > > > Thanks Ross. So sounds like it should be a matter of appending an > > addtask at the relevant part of each recipe -- is it that > > straightforward or have I overlooked anything important? > > Using a class you can add tasks for all recipes. If you explain what you're > actually trying to do then we can give better advice.
I'm thinking of a full build separated into say 3 sequential steps, A, B, and C, with each step being some series of bitbake tasks. The idea is run all the tasks in step A and then regain control so I can run some additional tools/transforms on artifacts (eg signing) produced in that step. Then, resume bitbake from step B, and after that completes then again regain control and run some additional transforms. Finally resume bitbake from step C and let that run to completion as well. I wasn't sure whether the bitbake has that sort of "pause and resume" capability, tho perhaps the addtask in the right places is one way to effect a similar result? (Apologies, this is probably a lame/awkward description on my part) Thanks again, Ed -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
