Re: [Qemu-devel] QEMU and Kconfig

[Samuel Ortiz]

On Wed, Nov 07, 2018 at 05:24:14PM -0200, Eduardo Habkost wrote:
> On Wed, Nov 07, 2018 at 06:39:54PM +0100, Paolo Bonzini wrote:
> > On 07/11/2018 16:41, Samuel Ortiz wrote:
> > > - The Kconfig parser would be used to generate the equivalent of what we
> > >   currently have under default-configs/
> > 
> > It would be used to generate config-devices.mak, instead of
> > scripts/make_device_config.sh.  My branch already had some Makefile
> > integration.
> > 
> > > - From a user's build perspective, there would be no noticeable
> > >   difference, ./configure && make. Internally, both steps will consume
> > >   the *.mak files generated by minikconf.
> > 
> > Right.  The only difference is that a user could do "./configure && make
> > randconfig && make" and similar.
> 
> Also, I would like to eventually replace many ./configure options
> with options read from a build configuration file.
> 
> Distributions often have huge ./configure command lines in their
> QEMU packages, and they could be replaced by simple build
> configuration files.
> 
> Having a mode that requires all build options to be specified
> explicitly (instead of silently picking a default)
I agree. This has been a problem for us several times, we saw build
errors because on some host build options were silently selected while
on others they were not.
But to emphasize on what Paolo said, I think using kconfig for
describing the target/device/platform dependencies is almost orthogonal
to improving the configuration step.

Cheers,
Samuel.