Writing a Player interface

From The Player Project

Jump to: navigation, search
m (Example Plugin Interface)
 
Line 20: Line 20:
<pre>
<pre>
-
/usr/local/share/player/examples/plugins/exampleplugin/
+
/usr/local/share/player/examples/plugins/exampleinterface/
</pre>
</pre>
Line 115: Line 115:
char doStuff;
char doStuff;
} player_eginterf_cmd_t;
} player_eginterf_cmd_t;
-
Generally, the structures will be named in some way that corresponds with the message types they go with. The names of the structures are usually in the form of "player_interfacename_structname"
 
</pre>
</pre>
 +
 +
Generally, the structures will be named in some way that corresponds with the message types they go with. The names of the structures are usually in the form of "player_interfacename_structname"
 +
===Building the interface===
===Building the interface===
Line 129: Line 131:
</pre>
</pre>
-
The build directory should now contain the shared objects for the plugin interface, and the header files that generated from the interface definition file.
+
The build directory should now contain the shared objects for the plugin interface, and the header files that generated from the interface definition file. For more information on building plugin interfaces, see the section on [[Compiling_Player_3_clients_and_plugins#Compiling_plugin_interfaces | Compiling plugin interfaces]]
== Static Interfaces ==
== Static Interfaces ==

Latest revision as of 11:26, 14 February 2011

Personal tools