From 2954eb7b358ce16ccff77e3f9523406454f500f1 Mon Sep 17 00:00:00 2001 From: Justin Clift Date: Tue, 21 Dec 2010 20:38:37 +1100 Subject: [PATCH] docs: added compiling page and significantly expanded windows page Also added an additional menu placement for the windows page, in order to attract further potential testers. --- docs/compiling.html.in | 75 +++++++++++++ docs/downloads.html.in | 41 +------ docs/sitemap.html.in | 10 ++ docs/windows.html.in | 237 ++++++++++++++++++++++++++++++++++++++--- 4 files changed, 310 insertions(+), 53 deletions(-) create mode 100644 docs/compiling.html.in diff --git a/docs/compiling.html.in b/docs/compiling.html.in new file mode 100644 index 0000000000..49bc7ee860 --- /dev/null +++ b/docs/compiling.html.in @@ -0,0 +1,75 @@ + + + +

libvirt Installation

+ + + +

Compiling a release tarball

+ +

+ libvirt uses the standard configure/make/install steps: +

+ + 
+      $ gunzip -c libvirt-x.x.x.tar.gz | tar xvf -
+      $ cd libvirt-x.x.x
+      $ ./configure
+ +

+ The configure script can be given options to change its default + behaviour. +

+ +

+ To get the complete list of the options it can take, pass it the + --help option like this: +

+ + 
+      $ ./configure --help
+ +

+ When you have determined which options you want to use (if any), + continue the process. +

+ +

+ Note the use of sudo with the make install command + below. Using sudo is only required when installing to a location your + user does not have write access to. Installing to a system location + is a good example of this. +

+ +

+ If you are installing to a location that your user does have write + access to, then you can instead run the make install command + without putting sudo before it. +

+ + 
+      $ ./configure [possible options]
+      $ make
+      $ sudo make install
+ +

+ At this point you may have to run ldconfig or a similar utility + to update your list of installed shared libs. +

+ +

Building from a GIT checkout

+ +

+ 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 autogen.sh command, passing the extra + arguments as for configure. As an example, to do a complete build and + install it into your home directory run: +

+ + 
+      $ ./autogen.sh --prefix=$HOME/usr --enable-compile-warnings=error
+      $ make
+      $ sudo make install
+ + diff --git a/docs/downloads.html.in b/docs/downloads.html.in index 709bee8be1..64a16c9f37 100644 --- a/docs/downloads.html.in +++ b/docs/downloads.html.in @@ -91,46 +91,9 @@
-

libvirt Installation

- -

Compiling a release tarball

-

- libvirt uses the standard configure/make/install steps: + Once you've have obtained the libvirt source code, you can compile it + using the instructions here.

- - 
-      gunzip -c libvirt-xxx.tar.gz | tar xvf -
-      cd libvirt-xxxx
-      ./configure --help
- -

- To see the options, then the compilation/installation proper: -

- - 
-      ./configure [possible options]
-      make
-      make install
- -

- At that point you may have to rerun ldconfig or a similar utility to - update your list of installed shared libs. -

- -

Building from a GIT checkout

- -

- 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 autogen.sh command, passing the extra - arguments as for configure. As an example, to do a complete build and - install it into your home directory run: -

- - 
-      ./autogen.sh --prefix=$HOME/usr --enable-compile-warnings=error
-      make
-      make install
diff --git a/docs/sitemap.html.in b/docs/sitemap.html.in index 7db59a1ec3..63e420fc92 100644 --- a/docs/sitemap.html.in +++ b/docs/sitemap.html.in @@ -21,11 +21,21 @@
  • Downloads Get the latest source releases, binary builds and get access to the source repository +
  • Documentation Information for users, administrators and developers