External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-22 21:55:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

Minor fixes for API extension doc

Browse Source 
Update the API Extensions doc to reflect new source directory layout.
This commit is contained in:
Jim Fehlig 2010-01-15 10:45:18 -07:00
parent 74ec5e65ce
commit 8d6af63a8a
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/api_extension.html.in
View File

@ -178,7 +178,7 @@
involves making two additions to:
</p>
<p><code>qemud/remote_protocol.x</code></p>
<p><code>src/remote/remote_protocol.x</code></p>
<p>
First, create two new structs for each new function that you're adding
@ -198,7 +198,7 @@
<p>
Once these changes are in place, it's necessary to run 'make rpcgen'
in the qemud directory to create the .c and .h files required by the
in the src directory to create the .c and .h files required by the
remote protocol code. This must be done on a Linux host using the
GLibC rpcgen program. Other rpcgen versions may generate code which
results in bogus compile time warnings
@ -213,7 +213,7 @@
the rpcgen generated .h files. The remote method calls go in:
</p>
<p><code>src/remote_internal.c</code></p>
<p><code>src/remote/remote_internal.c</code></p>
<p>Each remote method invocation does the following:</p>
@ -243,7 +243,7 @@
The server side dispatchers are implemented in:
</p>
<p><code>qemud/remote.c</code></p>
<p><code>daemon/remote.c</code></p>
<p>Again, this step uses the .h files generated by make rpcgen.</p>