
By convention, sample file names contain their respective (top-level)
IDL module name; the latter is also the sample directory name.

- <module name>.idl file   -- interface definition and necessary types.

- <module name>Impl.h file -- declares the VMCF 'implementation class' and
                              corresponds to the IDL-defined interface.

- <module name>Impl.c file -- contains the VMCF 'class' definition, including
                              instance variables, method implementations,
                              constructor, initializer and finalizer functions.

- <module name>Server.c file -- provides the server main function which
                                initializes VMCF, creates a VMCF server and
                                instantiates an object whose implementation
                                resides in <module name>Impl.c.

- <module name>Client.c file -- sample client code that invokes the object.


Building
-------- 
Please edit the samples/samples-{linux | windows}.make file(s) and update
the variables which are set to CHANGEME, to valid values according to the
SDK installation location for your platform.

Building a sample client and server:
(note that you must run 'make' from within the respective sample directory)
  $ cd samples/<sample>
  $ make VMCF_MODULE=<sample> -f ../samples-linux.make all

Or, on Windows:
  $ cd samples\<sample>
  $ nmake VMCF_MODULE=<sample> -f ..\samples-windows.make all

For example:
  $ cd samples/HelloWorld
  $ make VMCF_MODULE=HelloWorld -f ../samples-linux.make clean all

Running
-------
Please set your LD_LIBRARY_PATH (Linux), or PATH (Windows) environment
variables to include the location of the installed VMCF shared libraries.

Once built, please launch the client and server executables without any
arguments to obtain the their respective command line syntax.

