I am defining a meta-layer with our business logic (applications), one or two recipes and an image definition. I would like to maintain the C/C++ sources with this meta-layer in a single repository, because they are tightly coupled from a lifecycle perspective.
Is there a way to always build the current state of the source-code from a path relative to the recipe.bb file in a workflow friendly way? After scouring the web and mailing lists for days, I have no satisfactory answer. With OpenWRT, Buildroot 2 and ptxdist this was extremely simple to achieve. My requirements are: * Treat the meta-layer, it's recipes and images as well as package source-code as a monolithic whole with a single lifecycle within a single git repository, * Have the current checked out state of git repository built whenever I bake an image, * Not have things fall apart when I check-out in another location. I do not mind having to do a commit before each build so that the state can be tracked, but having to push and edit the recipe with the new commit ID so every change can be built deployed and tested is driving me nuts, especially since some changes are cross application, requiring an atomic update of both applications.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#48395): https://lists.yoctoproject.org/g/yocto/message/48395 Mute This Topic: https://lists.yoctoproject.org/mt/71245615/21656 Mute #yocto: https://lists.yoctoproject.org/mk?hashtag=yocto&subid=6691583 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
