On 12/20/2010 09:28 AM, Justin Clift wrote:
Also added an additional menu placement for the windows page, in order to attract further potential testers. --- This version of the patch includes information on TLS certificate files, connection types, and ESX/vSphere.
+ + <h2><a name="Compilatio">Compiling a release tarball</a></h2>
Any reason to truncate the name at Compilatio?
+ + <p> + libvirt uses the standard configure/make/install steps: + </p> + + <pre> + gunzip -c libvirt-xxx.tar.gz | tar xvf - + cd libvirt-xxxx
3 xxx vs. 4 xxxx in the two lines should be consistent.
+ <pre> + ./configure [possible options] + make + make install</pre>
Maybe list the last line as: [sudo] make install to help point out that installation is the only part of the process that must be run as root when doing a system-wide install, but that root rights are not needed when installing somewhere under $HOME for a single user?
+++ b/docs/downloads.html.in @@ -91,46 +91,9 @@
<br />
- <h1><a name="installation">libvirt Installation</a></h1> - - <h2><a name="Compilatio">Compiling a release tarball</a></h2>
Oh - just doc motion from the earlier incomplete name. But now that the target is on a new page, we might as well fix the target name.
+ + <li> + Libvirt dll files should be added to path + <br /><br /> + At the moment, anything that needs to use the libvirt dll files + (ie the C# bindings) won't automatically find them. This can be
s/ie/i.e./
+ worked around by copying the dll files into the same directory as + whatever needs them, but is probably not an optimal approach. + There might be a better way and needs to be investigated.
Requiring features of libtool 2.4 supposedly makes this easier, but yes, it does need more investigation. I hope to get further on a cygwin port of libvirt someday, at which point I'll have to provide updates for this page. -- Eric Blake eblake@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org