mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-28 08:35:22 +00:00
3e7db8d3e8
Right-aligning backslashes when defining macros or using complex commands in Makefiles looks cute, but as soon as any changes is required to the code you end up with either distractingly broken alignment or unnecessarily big diffs where most of the changes are just pushing all backslashes a few characters to one side. Generated using $ git grep -El '[[:blank:]][[:blank:]]\\$' | \ grep -E '*\.([chx]|am|mk)$$' | \ while read f; do \ sed -Ei 's/[[:blank:]]*[[:blank:]]\\$/ \\/g' "$f"; \ done Signed-off-by: Andrea Bolognani <abologna@redhat.com> |
||
---|---|---|
.. | ||
README | ||
vbox_CAPI_v4_0.h | ||
vbox_CAPI_v4_1.h | ||
vbox_CAPI_v4_2_20.h | ||
vbox_CAPI_v4_2.h | ||
vbox_CAPI_v4_3_4.h | ||
vbox_CAPI_v4_3.h | ||
vbox_CAPI_v5_0.h | ||
vbox_CAPI_v5_1.h | ||
vbox_common.c | ||
vbox_common.h | ||
vbox_driver.c | ||
vbox_driver.h | ||
vbox_get_driver.h | ||
vbox_glue.c | ||
vbox_glue.h | ||
vbox_MSCOMGlue.c | ||
vbox_MSCOMGlue.h | ||
vbox_network.c | ||
vbox_snapshot_conf.c | ||
vbox_snapshot_conf.h | ||
vbox_storage.c | ||
vbox_tmpl.c | ||
vbox_uniformed_api.h | ||
vbox_V4_0.c | ||
vbox_V4_1.c | ||
vbox_V4_2_20.c | ||
vbox_V4_2.c | ||
vbox_V4_3_4.c | ||
vbox_V4_3.c | ||
vbox_V5_0.c | ||
vbox_V5_1.c | ||
vbox_XPCOMCGlue.c | ||
vbox_XPCOMCGlue.h |
Licensing Note that much of the vbox in this directory is LGPLv2-only. Thus, it cannot be linked into any software that also wants to use GPLv3+ code. This readme file is: Copyright (C) 2009, 2013 Red Hat, Inc. Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. This file is offered as-is, without warranty of any kind. Explanation about the how multi-version support for VirtualBox libvirt driver is implemented. Since VirtualBox adds multiple new features for each release, it is but natural that the C API which VirtualBox exposes is volatile across versions and thus needs a good mechanism to handle multiple versions during runtime. The solution was something like this: Firstly the file structure is as below: vbox_CAPI_v2_2.h vbox_XPCOMCGlue.h vbox_XPCOMCGlue.c These files are C API/glue code files directly taken from the VirtualBox OSE source and is needed for C API to work as expected. vbox_driver.h vbox_driver.c These files have the main logic for registering the virtualbox driver with libvirt. vbox_V2_2.c The file which has version dependent changes and includes the template file for given below for all of its functionality. vbox_tmpl.c The file contains all version specified codes. It implements the vboxUniformedAPI for each vbox version. vbox_common.c The file implement the common driver, with the uniformed api which defined in vbox_uniformed_api.h and implemented in vbox_tmpl.c Now there would be a vbox_V*.c file (for eg: vbox_V2_2.c for V2.2) for each major virtualbox version which would do some preprocessor magic and include the template file (vbox_tmpl.c) in it for the functionality it offers.