From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60931) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gKh2R-0000ed-2D for qemu-devel@nongnu.org; Thu, 08 Nov 2018 04:55:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gKh2I-0001OD-K2 for qemu-devel@nongnu.org; Thu, 08 Nov 2018 04:55:45 -0500 Received: from mx1.redhat.com ([209.132.183.28]:34010) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gKh2G-00016P-IH for qemu-devel@nongnu.org; Thu, 08 Nov 2018 04:55:38 -0500 References: <20180924092120.GA30163@caravaggio> <7c2b477e-bdac-c887-2510-82fe04acdcfe@redhat.com> <87b22690-e39c-3b46-dcb4-f6abc3213142@redhat.com> <41ceda53-467e-32a1-8fa6-13f0f9c08ad1@redhat.com> <20181107154114.GC27585@caravaggio> <20181107192414.GH12503@habkost.net> From: Paolo Bonzini Message-ID: Date: Thu, 8 Nov 2018 10:55:21 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] QEMU and Kconfig List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Thomas Huth , Eduardo Habkost Cc: Samuel Ortiz , "Zhong, Yang" , Peter Maydell , QEMU Developers On 07/11/2018 20:30, Thomas Huth wrote: > On 2018-11-07 20:24, 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 wha= t we >>>> currently have under default-configs/ >=20 > I think we would still have something like default-configs - but there > would only be the bare minimum config switches in there, the rest would > be pulled in by dependencies. Yes, in theory default-configs would end up empty, except for possibly some commented lines to show the "default y" symbols for the target. > We could then also even have multiple config directories: >=20 > ./configs > +-------/default-softmmu > +-------/default-linux-user > +-------/nemu (or lean-kvm or something similar) > +... >=20 > ... just my 0.02 =E2=82=AC, feel free to ignore that idea ;-) Yup, one can also think of a configure option like "./configure --with-device-config=3Dconfigs/nemu/" to pick up the alternative configurations. >> 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. >=20 > I think we should maybe not mix host configuration (via ./configure) an= d > the target configuration (via kconfig), should we? Yeah, the configure command line is a different story. If there are suggestion on how to improve it, great, but let's not conflate it with Kconfig. Paolo