qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC PATCH 1/5] ppc64: Express dependencies of 'pseries


From: Thomas Huth
Subject: Re: [Qemu-devel] [RFC PATCH 1/5] ppc64: Express dependencies of 'pseries' and 'powernv' machines with kconfig
Date: Wed, 30 Jan 2019 11:02:02 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1

On 2019-01-30 10:57, Paolo Bonzini wrote:
> On 30/01/19 10:43, Thomas Huth wrote:
>> CONFIG_SPAPR_RNG should stay in the ppc-softmmu.mak file since this
>> is a completely optional device.
> 
> What about making it
> 
>     default y
> 
> and adding to the .mak file this:
> 
> #CONFIG_SPAPR_RNG=n
> 
> I think the two approaches are more or less equivalent, but
> "#CONFIG_FOO=n" has a small advantage when the feature has a build-time
> dependency, such as CONFIG_MILKYMIST_TMU2's dependency on OpenGL.  In
> that case,
> 
>    CONFIG_MILKYMIST_TMU2=y
> 
> would report a contradiction if OpenGL is not available at build time, while
> 
>    default y
>    ...
>    #CONFIG_MILKYMIST_TMU2=n
> 
> would not.

I somehow dislike the idea of adding lines that are commented out by
default. For example, if someone later renames or removes the config
switch in the Kconfig files, the comment could stay there without being
noticed, while a CONFIG_XXX=y would cause a clean build failure if the
option is not available anymore.

 Thomas



reply via email to

[Prev in Thread] Current Thread [Next in Thread]