1,079
edits
Difference between revisions of "HOWTO-Engines"
Jump to navigation
Jump to search
→Steps: instead of editing engines/module.mk one has to edit engines/engine.mk these days
Salty-horse (talk | contribs) (→Steps: Update the "configure" instruction. typos.) |
(→Steps: instead of editing engines/module.mk one has to edit engines/engine.mk these days) |
||
| Line 17: | Line 17: | ||
# Add <tt>engines/quux/module.mk</tt> (take a look at module.mk files of 2-3 existing engines to understand the content). | # Add <tt>engines/quux/module.mk</tt> (take a look at module.mk files of 2-3 existing engines to understand the content). | ||
# 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). It will also contain the plugin interface code (more on that in the next section). | # 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). It will also contain the plugin interface code (more on that in the next section). | ||
# Modify <tt>engines/ | # 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>configure</tt> by adding a new add_engine line. Again, just check out what is done for the existing engines. | # Modify <tt>configure</tt> by adding a new add_engine line. Again, just check out what is done for the existing engines. | ||
# Modify <tt>base/plugins.cpp</tt>; in particular, you have to add your engine to the list in PluginManager::loadPlugins. | # Modify <tt>base/plugins.cpp</tt>; in particular, you have to add your engine to the list in PluginManager::loadPlugins. | ||