mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-26 03:21:44 +03:00
313e628a76
Debian always runs autoreconf at package build time, which means that apt-get build-dep will bring in everything that's needed to build libvirt from a git clone; Fedora and RHEL, however, skip this step, so we have to install some extra packages manually. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
47 lines
1.1 KiB
ReStructuredText
47 lines
1.1 KiB
ReStructuredText
=======================
|
|
Contributing to libvirt
|
|
=======================
|
|
|
|
Full, up to date information on how to contribute to libvirt can be
|
|
found on the libvirt website:
|
|
|
|
https://libvirt.org/contribute.html
|
|
|
|
To build the same document locally, from the top level directory of
|
|
your git clone run:
|
|
|
|
::
|
|
|
|
$ mkdir build && cd build
|
|
$ ../autogen.sh
|
|
$ make
|
|
|
|
You'll find the freshly-built document in ``docs/contribute.html``.
|
|
|
|
If ``configure`` fails because of missing dependencies, you can set
|
|
up your system by calling
|
|
|
|
::
|
|
|
|
$ sudo dnf builddep libvirt
|
|
|
|
if you're on a RHEL-based distribution or
|
|
|
|
::
|
|
|
|
$ sudo apt-get build-dep libvirt
|
|
|
|
if you're on a Debian-based one.
|
|
|
|
Note that, for the RHEL-based case, if you're on a machine where you
|
|
haven't done any C development before, you will probably also need
|
|
to run
|
|
|
|
::
|
|
|
|
$ sudo dnf install gcc make libtool autoconf automake rpm-build
|
|
|
|
You might still be missing some dependencies if your distribution is
|
|
shipping an old libvirt version, but that will get you much closer to
|
|
where you need to be to build successfully from source.
|