[yocto] Append to bblayers.conf and local.conf

[Olsson Rikard (RBSN/ESW1)]

Hello Nicolas,

Thanks for your answer. Will these two files conf/auto.conf and conf/site.conf be able to handle changes for bblayers.conf as well?

For example we need to add meta-qt5 but would prefer to append to the layers already there and not add our changes into bblayers.conf to avoid merge work.

Best regards
Rikard Olsson




> -----Original Message-----
> From: Nicolas Dechesne [mailto:nicolas.dechesne at linaro.org]
> Sent: den 4 april 2016 11:30
> To: Paul Eggleton <paul.eggleton at linux.intel.com>
> Cc: Olsson Rikard (RBSN/ESW1) <Rikard.Olsson at se.bosch.com>; Yocto list
> discussion <yocto at yoctoproject.org>
> Subject: Re: [yocto] Append to bblayers.conf and local.conf
> 
> On Sun, Apr 3, 2016 at 10:54 PM, Paul Eggleton <paul.eggleton at linux.intel.com>
> wrote:
> >> We are receiving bblayer.conf and local.conf from external supplier
> >> which already have layers/configuration added. Now we want to add our
> >> own layers/configuration by appending to these files this to avoid
> >> manual merge work each time a delivery from external supplier is made.
> >>
> >> Question:
> >> How do I append layers/configuration to bblayer.conf and local.conf?
> >
> > The best answer I can give is these files aren't really meant to be
> > distributed. If you have too much specific stuff in these files
> > (particularly
> > local.conf) then I would say it's possible your supplier has put
> > things in the wrong place.
> >
> > The way it ought to work is, you add the needed layers to your
> > bblayers.conf, then go to your local.conf and set DISTRO and MACHINE
> > and anything you need for *local* configuration (e.g. local paths) and
> > that's pretty much it. If you have to include a whole bunch of extra
> > lines in local.conf, those lines really should be elsewhere (e.g.
> > custom distro config, or the machine .conf file if they are specific
> > to the machine.)
> 
> Note that you can use conf/auto.conf and conf/site.conf as well, these files are
> parsed at the same time as conf/local.conf, so if you really cannot change
> local.conf, you can use the one of the other ones.