diff options
| author | Peter Krempa <pkrempa@redhat.com> | 2022-09-09 14:20:15 +0200 |
|---|---|---|
| committer | Peter Krempa <pkrempa@redhat.com> | 2022-09-13 13:36:49 +0200 |
| commit | 91284a2893a3f960bfa7274b3a10f156980d71af (patch) | |
| tree | b82a7eb308a84281e593343335d486a2e33817fd /docs | |
| parent | fbd6b2480aeeab048fd963c95682d7e9ce2a9a65 (diff) | |
| download | libvirt-91284a2893a3f960bfa7274b3a10f156980d71af.tar.gz | |
docs: compiling: Section off block on how to run from build directory
Running from build directory isn't strictly tied to the git-checkout
build so make a new section for it.
Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/compiling.rst | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/docs/compiling.rst b/docs/compiling.rst index 25dd0f4265..fc5556738d 100644 --- a/docs/compiling.rst +++ b/docs/compiling.rst @@ -98,10 +98,12 @@ normal OS vendor prefixes, use $ ninja -C build -When doing this for day-to-day development purposes, it is recommended -not to install over the OS vendor provided binaries. Instead simply run -libvirt directly from the source tree. For example to run a privileged -libvirtd instance +Running compiled binaries from build directory +---------------------------------------------- + +For testing or development purposes it's usually not necessary to install the +built binaries into your system. Instead simply run libvirt directly from the +source tree. For example to run a privileged libvirtd instance :: |