1. Messages
  2. #yocto Preferred development workflow

Re: #yocto Preferred development workflow #yocto

Chuck Wolber
 

You left a few details out about how the configuration files are managed. Ideally you could just make bitbake recipes for the config files themselves. This way you can create an image recipe for each project and use the IMAGE_INSTALL variable to append whatever configs and modules you want on a per-project basis.

..Ch:W..


On Mon, Jul 12, 2021 at 8:40 PM ivin.lim via lists.yoctoproject.org <ivin.lim=aei.com@...> wrote:
Hi everyone,

I'm curious on a good approach when dealing with multiple projects

I've just started out  yocto and have already  created our own meta-layer which contains our modules. Now these modules would sometimes have config files and this could vary when each project that we have would use these recipes. I'm thinking of a way to control this. And I don't think having one branch per project is a good style. Right now the best way I can think of is creating seperate "project layers" (ex. meta-project1, meta-project2) and from there create those .bbappends which would point to the project-specific conf files. 

But I was wondering if there is a better way of handling it. Thanks.

Cheers.




--
"Perfection must be reached by degrees; she requires the slow hand of time." - Voltaire
Join yocto@lists.yoctoproject.org to automatically receive all group messages.