56c56b3bf8
The colors are not based on the semantics of the message but rather on the message itself. This means that the default human-perceived semantics (red = bad, green = good) don't really apply and spotting a color does not mean anythting. This is amplified by the sheer amount of output which configure produces and the fact that some of the messages have negative semantics or additional output. In case of any problem the user will have to go through everything anyways as spotting a red or yellow line has 0 information value. Here are a few examples: 1) some 'no' messages are not a problem: checking minix/config.h presence... no 2) some 'no' messages are actually positive: checking for special C compiler options needed for large files... no 3) in some cases a 'yes' would mean that something is broken or needs workaround checking whether stat file-mode macros are broken... no checking whether wint_t is too small... no checking whether stdint.h predates C++11... no checking whether the inttypes.h PRIxNN macros are broken... no checking whether clang gives bogus warnings for -Wdouble-promotion... no checking whether gettimeofday clobbers localtime buffer... no 4) due to string match based colors extra text makes messages yellow checking for a traditional french locale... none checking for working nanosleep... no (mishandles large arguments) checking for library containing gethostbyname... none required checking whether mbrtowc handles incomplete characters... (cached) guessing yes 5) in some cases the yes/no is very context dependant checking whether pthread_rwlock_rdlock prefers a writer to a reader... no checking whether this build is done by a static analysis tool... no 6) detected paths to binaries and libs are yellow despite being present checking for objdump... objdump checking for atomic ops implementation... gcc As of the reasons above I don't think the colorization of the configure output helps users or developers to debug the build process and thus is not worth the extra code or output clutter. This reverts commit c98174ce087fe23f567292132e961d4685faf337. ACKed-by: Michal Prívozník <mprivozn@redhat.com> Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Libvirt API for virtualization
Libvirt provides a portable, long term stable C API for managing the virtualization technologies provided by many operating systems. It includes support for QEMU, KVM, Xen, LXC, bhyve, Virtuozzo, VMware vCenter and ESX, VMware Desktop, Hyper-V, VirtualBox and the POWER Hypervisor.
For some of these hypervisors, it provides a stateful management daemon which runs on the virtualization host allowing access to the API both by non-privileged local users and remote users.
Layered packages provide bindings of the libvirt C API into other languages including Python, Perl, PHP, Go, Java, OCaml, as well as mappings into object systems such as GObject, CIM and SNMP.
Further information about the libvirt project can be found on the website:
License
The libvirt C API is distributed under the terms of GNU Lesser General
Public License, version 2.1 (or later). Some parts of the code that are
not part of the C library may have the more restrictive GNU General
Public License, version 2.0 (or later). See the files COPYING.LESSER
and COPYING for full license terms & conditions.
Installation
Libvirt uses the GNU Autotools build system, so in general can be built and installed with the usual commands. For example, to build in a manner that is suitable for installing as root, use:
$ ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
$ make
$ sudo make install
While to build & install as an unprivileged user
$ ./configure --prefix=$HOME/usr
$ make
$ make install
The libvirt code relies on a large number of 3rd party libraries. These will
be detected during execution of the configure script and a summary printed
which lists any missing (optional) dependencies.
Contributing
The libvirt project welcomes contributions in many ways. For most components the best way to contribute is to send patches to the primary development mailing list. Further guidance on this can be found on the website:
https://libvirt.org/contribute.html
Contact
The libvirt project has two primary mailing lists:
- libvirt-users@redhat.com (for user discussions)
- libvir-list@redhat.com (for development only)
Further details on contacting the project are available on the website: