
14 Apr
2016
14 Apr
'16
1:59 p.m.
Dario Faggioli writes ("Re: [Xen-devel] Fixing libvirt's libxl driver breakage -- where to define LIBXL_API_VERSION?"):
And, in those cases, usage should be gated by the appropriate LIBXL_HAVE_FOOBAR symbol, which I see in the sources (e.g., for LIBXL_HAVE_NO_SUSPEND_RESUME or LIBXL_HAVE_DOMAIN_NODEAFFINITY) to be the case, so good again. :-)
If libvirt specifies LIBXL_API_VERSION then it does not need to check any LIBXL_HAVE_*, since it will actually get an API corresponding to the specified API_VERSION. Ian.