Open main menu

Difference between revisions of "HOWTO-Engines"

304 bytes removed ,  10:35, 26 November 2013
→‎Steps: Update section on steps required for adding a new engine
(Make clear that no audio device (i.e. MIDI) initialization should be done in the constructor either)
(→‎Steps: Update section on steps required for adding a new engine)
Line 15: Line 15:


# Add a new directory <tt>engines/quux/</tt>
# Add a new directory <tt>engines/quux/</tt>
# Add <tt>engines/quux/module.mk</tt> (looking at module.mk files of existing engines should make it clear what you have to do).
# Add <tt>engines/quux/configure.engine</tt> (looking at configure.engine files of existing engines should make it clear what you have to do).
# Add <tt>engines/quux/module.mk</tt> (Again, just check out what is done for the existing engines).
# Add <tt>engines/quux/quux.h</tt> and <tt>engines/quux/quux.cpp</tt>; this will contain your Engine subclass (or at least parts of it).
# Add <tt>engines/quux/quux.h</tt> and <tt>engines/quux/quux.cpp</tt>; this will contain your Engine subclass (or at least parts of it).
# Add <tt>engines/quux/detection.cpp</tt>; It will contain the plugin interface code (more on that in the next section).
# Add <tt>engines/quux/detection.cpp</tt>; It will contain the plugin interface code (more on that in the next section).
# Modify <tt>engines/engines.mk</tt> by adding your engine. It should be clear what to do by looking at what is done for the other engines there.
# Modify <tt>engines/configure.engines</tt> by adding a new add_engine line. Again, just check out what is done for the existing engines.
# Modify <tt>engines/plugins_table.h</tt>; It should be pretty straightforward to do this by checking out how the other engines do it.


That's it. The difficult part is of course writing the Engine subclass. More on that in the next section!
That's it. The difficult part is of course writing the Engine subclass. More on that in the next section!
561

edits