Update the API Extensions doc to reflect new source directory layout. --- docs/api_extension.html.in | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/api_extension.html.in b/docs/api_extension.html.in index 59d3414..de6eedc 100644 --- a/docs/api_extension.html.in +++ b/docs/api_extension.html.in @@ -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> --