| commit | 1a34904e5b59fd42f238dc50992af1c3a11a458b | |
| author | Michael Roth <mdroth@linux.vnet.ibm.com> | |
| Wed, 26 Aug 2015 16:14:31 +0000 (26 11:14 -0500) | ||
| committer | Michael Roth <mdroth@linux.vnet.ibm.com> | |
| Tue, 1 Sep 2015 18:16:26 +0000 (1 13:16 -0500) | ||
| tree | da5abdb62264373e9f6e5e35383083b3b3dbb71e | treesnapshot (tar.gz zip) |
| parent | 9d6bc27b7e0e8520f1f91721d9c738e027eeb6c4 | commitdiff |
configure: qemu-ga: explicitly enable qemu-ga MSI support when probed
Currently, if we don't explicitly disable support for MSI installer
via --disable-guest-agent-msi, the configure variable that tracks
the flag, 'guest_agent_msi', never gets set unless one of the probes
fails. Subsequent code then treats this unset value the same as if it
were a "yes" value (via != "no" style checks).
Instead, set the default "yes" value explicitly after the probes, then
make subsequent code expect the values to be set.
This makes it easier to report on whether or not MSI support was
enabled via probe by looking at the ./configure summary.
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Currently, if we don't explicitly disable support for MSI installer
via --disable-guest-agent-msi, the configure variable that tracks
the flag, 'guest_agent_msi', never gets set unless one of the probes
fails. Subsequent code then treats this unset value the same as if it
were a "yes" value (via != "no" style checks).
Instead, set the default "yes" value explicitly after the probes, then
make subsequent code expect the values to be set.
This makes it easier to report on whether or not MSI support was
enabled via probe by looking at the ./configure summary.
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
| configure | diffblobblamehistory |