960
edits
Difference between revisions of "HOWTO-Backends"
Jump to navigation
Jump to search
m
Fixed for coherence
(→Step by step: This page was (is) heavily outdated -- made some fixes) |
m (Fixed for coherence) |
||
| Line 16: | Line 16: | ||
In the following I assume your port is named "foobar" (very clever, isn't it? :-). | In the following I assume your port is named "foobar" (very clever, isn't it? :-). | ||
# Create a new <code>backends/platform</code> subdirectory matching your | # Create a new <code>backends/platform</code> subdirectory matching your port name, i.e. <tt>backends/platform/foobar/</tt> | ||
# Populate the new directory as you need to. If you want to use our regular build system, you will want to provide <tt>backends/foobar/module.mk</tt> file. Take a look at <code>backends/platform/sdl/module.mk</code> for an example. | # Populate the new directory as you need to. If you want to use our regular build system, you will want to provide <tt>backends/platform/foobar/module.mk</tt> file. Take a look at <code>backends/platform/sdl/module.mk</code> for an example. | ||
# Subclass OSystem. You could copy the content of <tt>backends/platform/null/null.cpp</tt> to <tt>backends/platform/foobar/foobar.cpp</tt> to get a skeleton. As you progress, it might be helpful to look at other backends to learn how they do things. | # Subclass OSystem. You could copy the content of <tt>backends/platform/null/null.cpp</tt> to <tt>backends/platform/foobar/foobar.cpp</tt> to get a skeleton. As you progress, it might be helpful to look at other backends to learn how they do things. | ||
# Make sure to provide the <tt>main</tt> function in your backend (the actual main function of ScummVM is <tt>scummvm_main</tt>, which your backend must invoke at some point). | # Make sure to provide the <tt>main</tt> function in your backend (the actual main function of ScummVM is <tt>scummvm_main</tt>, which your backend must invoke at some point). | ||