Re: [libvirt] [PATCH] Improve docs about compiling libvirt from GIT
On 05/24/2012 08:38 PM, Daniel P. Berrange wrote: From: Daniel P. Berrange berra...@redhat.com Add a note about setting the LIBVIRT_DRIVER_DIR env variable, explain --system and fix example to use --disable-werror --- docs/compiling.html.in | 51 1 file changed, 47 insertions(+), 4 deletions(-) diff --git a/docs/compiling.html.in b/docs/compiling.html.in index 49bc7ee..5a9d9ee 100644 --- a/docs/compiling.html.in +++ b/docs/compiling.html.in @@ -62,14 +62,57 @@ 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 codeautogen.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: + templates using the codeautogen.sh/code command. By default when + the codeconfiure/code script is run from within a GIT checkout, it s/confiure/configure + will turn on -Werror for builds. This can be disabled with --disable-werror, + but this is not recommended. To build amp; install libvirt to your home + directory the following commands can be run: /p pre - $ ./autogen.sh --prefix=$HOME/usr --enable-compile-warnings=error + $ ./autogen.sh --prefix=$HOME/usr $ make $ bsudo/b make install/pre + +p + Be aware though, that binaries built with a custom prefix will not + interoperate with OS vendor provided binaries, since the UNIX socket + paths will all be different. To produce a build that is compatible + with normal OS vendor prefixes, using s/using/use +/p + +pre + $ ./autogen.sh --system + $ make +/pre + +p + When doing this for day-to-day development purposes, it is recommended + not to install over the to OS vendor provided binaries. Instead simply must have been over to the ? + run libvirt directory from the source tree. For example to run s/directory/directly + a privileged libvirtd instance +/p + +pre + $ su - + # service libvirtd stop (or systemctl stop libvirtd.service) + # /home/to/your/checkout/daemon/libvirtd +/pre + +p + It is also possible to run virsh directly from the source tree +/p + +pre + $ ./tools/virsh +/pre + +p + A normal configuration of libvirt will build hypervisor drivers + as loadable modules. When runnning from a non-installed source s/runnning/running + tree, libvirtd will attempt to find the modules from the same + source tree. If this is not possible though, you can explicitly + set codeLIBVIRT_DRIVER_DIR=/path/to/source/tree/src/.libs/code +/p /body /html Regards, Srivatsa S. Bhat -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH] Improve docs about compiling libvirt from GIT
On Fri, May 25, 2012 at 12:48:12PM +0530, Srivatsa S. Bhat wrote: On 05/24/2012 08:38 PM, Daniel P. Berrange wrote: From: Daniel P. Berrange berra...@redhat.com Add a note about setting the LIBVIRT_DRIVER_DIR env variable, explain --system and fix example to use --disable-werror --- docs/compiling.html.in | 51 1 file changed, 47 insertions(+), 4 deletions(-) Thanks, pushing with all the various typos fixed Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] [PATCH] Improve docs about compiling libvirt from GIT
From: Daniel P. Berrange berra...@redhat.com Add a note about setting the LIBVIRT_DRIVER_DIR env variable, explain --system and fix example to use --disable-werror --- docs/compiling.html.in | 51 1 file changed, 47 insertions(+), 4 deletions(-) diff --git a/docs/compiling.html.in b/docs/compiling.html.in index 49bc7ee..5a9d9ee 100644 --- a/docs/compiling.html.in +++ b/docs/compiling.html.in @@ -62,14 +62,57 @@ 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 codeautogen.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: + templates using the codeautogen.sh/code command. By default when + the codeconfiure/code script is run from within a GIT checkout, it + will turn on -Werror for builds. This can be disabled with --disable-werror, + but this is not recommended. To build amp; install libvirt to your home + directory the following commands can be run: /p pre - $ ./autogen.sh --prefix=$HOME/usr --enable-compile-warnings=error + $ ./autogen.sh --prefix=$HOME/usr $ make $ bsudo/b make install/pre + +p + Be aware though, that binaries built with a custom prefix will not + interoperate with OS vendor provided binaries, since the UNIX socket + paths will all be different. To produce a build that is compatible + with normal OS vendor prefixes, using +/p + +pre + $ ./autogen.sh --system + $ make +/pre + +p + When doing this for day-to-day development purposes, it is recommended + not to install over the to OS vendor provided binaries. Instead simply + run libvirt directory from the source tree. For example to run + a privileged libvirtd instance +/p + +pre + $ su - + # service libvirtd stop (or systemctl stop libvirtd.service) + # /home/to/your/checkout/daemon/libvirtd +/pre + +p + It is also possible to run virsh directly from the source tree +/p + +pre + $ ./tools/virsh +/pre + +p + A normal configuration of libvirt will build hypervisor drivers + as loadable modules. When runnning from a non-installed source + tree, libvirtd will attempt to find the modules from the same + source tree. If this is not possible though, you can explicitly + set codeLIBVIRT_DRIVER_DIR=/path/to/source/tree/src/.libs/code +/p /body /html -- 1.7.10.1 -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH] Improve docs about compiling libvirt from GIT
On 05/24/2012 05:08 PM, Daniel P. Berrange wrote: From: Daniel P. Berrange berra...@redhat.com Add a note about setting the LIBVIRT_DRIVER_DIR env variable, explain --system and fix example to use --disable-werror --- docs/compiling.html.in | 51 1 file changed, 47 insertions(+), 4 deletions(-) diff --git a/docs/compiling.html.in b/docs/compiling.html.in index 49bc7ee..5a9d9ee 100644 --- a/docs/compiling.html.in +++ b/docs/compiling.html.in @@ -62,14 +62,57 @@ 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 codeautogen.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: + templates using the codeautogen.sh/code command. By default when + the codeconfiure/code script is run from within a GIT checkout, it Didn't you mean codeconfigure/codethere ? ;-) Michal -- Michal Novotny minov...@redhat.com, RHCE, Red Hat Virtualization | libvirt-php bindings | php-virt-control.org -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
