2008-04-23 17:08:31 +00:00
|
|
|
<?xml version="1.0"?>
|
|
|
|
<html>
|
|
|
|
<body>
|
2010-09-10 09:26:05 +00:00
|
|
|
<h1>Downloads</h1>
|
2008-04-23 17:08:31 +00:00
|
|
|
|
|
|
|
<h2>Official Releases</h2>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
The latest versions of the libvirt C library can be downloaded from:
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
<li><a href="ftp://libvirt.org/libvirt/">libvirt.org FTP server</a></li>
|
|
|
|
<li><a href="http://libvirt.org/sources/">libvirt.org HTTP server</a></li>
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
<h2>Hourly development snapshots</h2>
|
|
|
|
|
|
|
|
<p>
|
2009-07-06 12:27:00 +00:00
|
|
|
Once an hour, an automated snapshot is made from the git server
|
2008-04-24 09:17:29 +00:00
|
|
|
source tree. These snapshots should be usable, but we make no guarantees
|
2008-04-23 17:08:31 +00:00
|
|
|
about their stability:
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<ul>
|
2009-07-06 12:27:00 +00:00
|
|
|
<li><a href="ftp://libvirt.org/libvirt/libvirt-git-snapshot.tar.gz">libvirt.org FTP server</a></li>
|
|
|
|
<li><a href="http://libvirt.org/sources/libvirt-git-snapshot.tar.gz">libvirt.org HTTP server</a></li>
|
2008-04-23 17:08:31 +00:00
|
|
|
</ul>
|
|
|
|
|
2010-09-10 09:26:05 +00:00
|
|
|
<h2>GIT source repository</h2>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
Libvirt code source is now maintained in a <a href="http://git-scm.com/">git</a>
|
|
|
|
repository available on <a href="http://libvirt.org/git/">libvirt.org</a>:
|
2008-04-23 17:08:31 +00:00
|
|
|
</p>
|
|
|
|
|
2010-09-10 09:26:05 +00:00
|
|
|
<pre>
|
|
|
|
git clone git://libvirt.org/libvirt.git</pre>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
It can also be browsed at:
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<pre>
|
|
|
|
<a href="http://libvirt.org/git/?p=libvirt.git;a=summary">http://libvirt.org/git/?p=libvirt.git;a=summary</a></pre>
|
|
|
|
|
|
|
|
<br />
|
|
|
|
|
|
|
|
<h1>libvirt Application Development Guide</h1>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
This is both a guide to developing with libvirt, and a useful
|
|
|
|
reference document. It is a work in progress, contributed to by the
|
|
|
|
members of the libvirt team and being authored by a professional
|
|
|
|
author.
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
Contributors to this are <b>VERY</b> welcome, so if you'd like to
|
|
|
|
get your name in this and demonstrate your virtualisation prowess,
|
|
|
|
contributing solidly to the content here will do it. :)
|
2008-04-23 17:08:31 +00:00
|
|
|
</p>
|
2010-09-10 09:26:05 +00:00
|
|
|
|
|
|
|
<h2>Downloadable PDF</h2>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
PDF download is available here:
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
<li><a href="http://libvirt.org/guide/pdf/Application_Development_Guide.pdf">libvirt App Dev Guide</a> (PDF)</li>
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
<h2>GIT source repository</h2>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
The source is also in a git repository:
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<pre>
|
|
|
|
git clone git://libvirt.org/libvirt-appdev-guide.git</pre>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
Browsable at:
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<pre>
|
|
|
|
<a href="http://libvirt.org/git/?p=libvirt-appdev-guide.git;a=summary">http://libvirt.org/git/?p=libvirt-appdev-guide.git;a=summary</a></pre>
|
|
|
|
|
|
|
|
<br />
|
|
|
|
|
|
|
|
<h1>libvirt Installation</h1>
|
|
|
|
|
|
|
|
<h2><a name="Compilatio" id="Compilatio">Compilation</a></h2>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
libvirt uses the standard configure/make/install steps:
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<pre>
|
|
|
|
gunzip -c libvirt-xxx.tar.gz | tar xvf -
|
|
|
|
cd libvirt-xxxx
|
|
|
|
./configure --help</pre>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
To see the options, then the compilation/installation proper:
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<pre>
|
|
|
|
./configure [possible options]
|
|
|
|
make
|
|
|
|
make install</pre>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
At that point you may have to rerun ldconfig or a similar utility to
|
|
|
|
update your list of installed shared libs.
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<h2>Building from a source code checkout</h2>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
The libvirt build process uses GNU autotools, so after obtaining a
|
|
|
|
checkout it is necessary to generate the configure script and Makefile.in
|
|
|
|
templates using the <code>autogen.sh</code> command, passing the extra
|
|
|
|
arguments as for configure. As an example, to do a complete build and
|
|
|
|
install it into your home directory run:
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<pre>
|
|
|
|
./autogen.sh --prefix=$HOME/usr --enable-compile-warnings=error
|
2008-04-23 17:08:31 +00:00
|
|
|
make
|
2010-09-10 09:26:05 +00:00
|
|
|
make install</pre>
|
2008-04-23 17:08:31 +00:00
|
|
|
</body>
|
|
|
|
</html>
|