[bitbake-devel] [PATCH] cookerdata.py: check for existence of configuration files

[Bystricky, Juro]

I see your point. The route via a dummy default.conf would require having 
the folder conf/multiconfig present even for users not really interested in 
multiconfig. Not a show stopper, it would be just another file created by
oe-init-build-env. (Another possibility is to have the error check as part 
of sanity checking)

> -----Original Message-----
> From: Richard Purdie [mailto:richard.purdie at linuxfoundation.org]
> Sent: Friday, January 13, 2017 2:55 AM
> To: Bystricky, Juro <juro.bystricky at intel.com>; bitbake-
> devel at lists.openembedded.org
> Cc: jurobystricky at hotmail.com
> Subject: Re: [PATCH] cookerdata.py: check for existence of configuration
> files
> 
> On Thu, 2017-01-12 at 15:40 -0800, Juro Bystricky wrote:
> > Presently there is no check to verify the existence of configuration
> > files as listed in BBMULTICONFIG. For example, BBMULTICONFIG =
> > "foobar" in local.conf
> > does not trigger an error when there is no
> > conf/multiconfig/foobar.conf.
> > The missing file is silently ignored.
> >
> > This patch verifies the existence of config files and errors-out with
> > the message:
> >
> > ERROR: BBMULTICONFIG="foobar" but the configuration file
> > './conf/multiconfig/foobar.conf' does not exist!
> >
> > when the file does not exist.
> >
> > [YOCTO#10917]
> 
> Sorry but we can't do this. One reason for some of the recent changes
> was to move the handling of this to the metadata and out of bitbake.
> We've therefore now got:
> 
> include conf/multiconfig/${BB_CURRENT_MC}.conf
> 
> in bitbake.conf and the system looks for the file that way. The user is
> free to add other files in other paths and bitbake doesn't know/care
> about the directory layout.
> 
> If we really want to make this error, we'd need to add an empty
> conf/multiconfig/default.conf and then change this to a require instead
> of an include. Bitbake's standard error messages would then kick in.
> 
> Cheers,
> 
> Richard