2008-04-23 17:08:31 +00:00
|
|
|
<html>
|
|
|
|
<body>
|
|
|
|
<h1>Deployment</h1>
|
|
|
|
|
|
|
|
<h2>Pre-packaged releases</h2>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
The libvirt API is now available in all major Linux distributions
|
|
|
|
so the simplest deployment approach is to use your distributions'
|
|
|
|
package management software to install the <code>libvirt</code>
|
|
|
|
module.
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<h2>Self-built releases</h2>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
libvirt uses GNU autotools for its build system, so deployment
|
|
|
|
follows the usual process of <code>configure; make ; make install</code>
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<pre>
|
|
|
|
|
|
|
|
# ./configure --prefix=$HOME/usr
|
|
|
|
# make
|
|
|
|
# make install
|
|
|
|
</pre>
|
|
|
|
|
|
|
|
<h2>Built from CVS / GIT</h2>
|
|
|
|
|
|
|
|
<p>
|
2008-05-15 06:12:32 +00:00
|
|
|
When building from CVS it is necessary to generate the autotools
|
2008-04-23 17:08:31 +00:00
|
|
|
support files. This requires having <code>autoconf</code>,
|
|
|
|
<code>automake</code>, <code>libtool</code> and <code>intltool</code>
|
|
|
|
installed. The process can be automated with the <code>autogen.sh</code>
|
|
|
|
script.
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<pre>
|
|
|
|
|
|
|
|
# ./autogen.sh --prefix=$HOME/usr
|
|
|
|
# make
|
|
|
|
# make install
|
|
|
|
</pre>
|
|
|
|
|
|
|
|
</body>
|
|
|
|
</html>
|