|
From: | Paolo Bonzini |
Subject: | Re: [Qemu-devel] [PULL v3 00/12] Final changes for 2.4-rc0 |
Date: | Fri, 24 Jul 2015 16:21:10 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0.1 |
On 24/07/2015 16:19, Daniel P. Berrange wrote: >> > Right... We need to introduce CONFIG_CRYPTO and use it in >> > tests/Makefile too. > Except it was a goal of this work that we do not have such config > parameters leak outside to callers. CONFIG_CRYPTO would disable all of crypto/ if neither tools nor system emulators are compiled (e.g. using $(call lor) and $(call notempty)). It would be an internal detail of the Makefile. Paolo > The intent was that the APIs > are always built-in - we just conditionally disable the internal > implementation, so that code using these APIs does not need to > deal with conditionally disabling itself like this. It is > preferrable to just fix disablement of gnutls IMHO.
[Prev in Thread] | Current Thread | [Next in Thread] |