You may download the current version of the user's manual. [pdf]
How to use DICE.
DICE is an IDL compiler. It translates interface specification into communication stubs. It is a tool, which component developers use to ease the implementation of the communication interface of their components. Thus you first need a definition of the communication interface of your component. Then you eventually translate this file using DICE to generate the communication stubs. Now you only have to find out how to use the generated communication stubs.
Interface Definition Language File
These files contain the definition of a component's interface. It may also define types and constants which are used by the interface. An interface is a collection of types and functions, which are supported by that interface. An interface may be derived from another interface. A derived interface supports all the functions and types of the base interface as well. To group interfaces and types namespace hierarchies can be created using modules (CORBA IDL) or libraries (DCE IDL).
Invoking DICE is pretty straigth forward. Opposed to the Flick approach,
where you have to invoke several pieces of the compiler seperately, DICE only
needs one call. The options of the current DICE version can be shown starting
DICE with no parameter or with
Using the generated Stubs
Now, that you generated stubs for your interface specification you would like to use it, right? All you have to do is to include the client header files, whereever you like to invoke services of your component and link the client objects to that code. The server component needs a bit more work. DICE may provide you with function skeletons, which you will have to fill with the appropriate code of your component. Now you have to build your component and voila, that's it. The stubs use a header file called "dice/dice.h". This header file is in the directory <dice-src>/include/.