On 3/3/20, Aaron Cohen <[email protected]> wrote: > devshell is good for playing around, but I don't know of any blessed way to > just have it somehow modify recipes and create patches magically. I'd be > interested to hear if there is something like that. > > The closest to what I think you want is the "devtool" workflow > <https://www.yoctoproject.org/docs/2.3/dev-manual/dev-manual.html#using-devtool-in-your-workflow> > > > Basically: > 1) devtool modify <recipe> > 2) hack source in $BUILDDIR/workspace/sources/<recipe>, test as desired by > using "bitbake <recipe>" or "bitbake <image containing recipe>" > # Once satisfied with changes: > 3) git add $BUILDDIR/workspace/sources/<recipe> && git commit -m "Added > cool changes to recipe" > 4) devtool finish <recipe> <your_layer_name>
I'm not sure that the git add is relevant for all recipes though. Some of them are simply tarball sources and others are shallow git archives. Should I be confident that yocto will know the difference and treat each case correctly? or more likely I'll assume that something was registered and then it doesn't find it's way into the build but slips through the cracks? So the question is whether devtool finish is smart enough to save the changes, regardless of whether the source repo is git or tarball.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#48683): https://lists.yoctoproject.org/g/yocto/message/48683 Mute This Topic: https://lists.yoctoproject.org/mt/71710407/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
