Re: [Qemu-devel] QEMU and Kconfig

From: Eduardo Habkost <ehabkost@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	"Zhong, Yang" <yang.zhong@intel.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Thomas Huth <thuth@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QEMU and Kconfig
Date: Wed, 7 Nov 2018 17:24:14 -0200	[thread overview]
Message-ID: <20181107192414.GH12503@habkost.net> (raw)
In-Reply-To: <dd68d3e8-6448-3a67-3212-fd3d3bfba2e2@redhat.com>

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) would be
useful for distributions, too.

-- 
Eduardo