Difference between revisions of "Compiling ScummVM/Windows CE"

Jump to navigation Jump to search
m
some phrasing & formatting
m (→‎Libraries: fix broken links)
m (some phrasing & formatting)
Line 39: Line 39:




Now you may be asking yourselves why we have been through so many compiler changes. There are absolutely critical reasons for switching between them.  
Why all these compiler changes? There are absolutely critical reasons for switching between them.  
For example, the migration from evc to VS is mandatory, as C++ templates introduced  
For example, the migration from evc to VS is mandatory, as C++ templates introduced  
through core code evolution in the trunk of ScummVM
through core code evolution in the trunk of ScummVM
Line 186: Line 186:
|}
|}
''Try <tt>make libz.a</tt> for libz. Also DrMcCoy reported that he had to include "<tt>typedef long _off_t; typedef _off_t  off_t;</tt>" into <tt>unistd.h</tt>''
''Try <tt>make libz.a</tt> for libz. Also DrMcCoy reported that he had to include "<tt>typedef long _off_t; typedef _off_t  off_t;</tt>" into <tt>unistd.h</tt>''
''WARNING: These instructions have been written with the VLC GCC compiler in mind. Exact command lines may differ slightly from these shown aboe''
''WARNING: These instructions have been written with the VLC GCC compiler in mind. Exact command lines may differ slightly from these shown aboe''


Line 204: Line 205:


* Build
* Build
cd into <tt>backends/platform/wince/</tt>, edit the Makefile to your needs (usually you don't have to do this). Finally type <tt>make dist</tt> if you have edited the Makefile for a non-plugin build, <tt>make dist-plugins</tt> for the plugin case, or more simply <tt>make all</tt> which invokes the required build automatically.
cd into <tt>backends/platform/wince/</tt>, edit the Makefile to your needs (usually you don't have to do this). Finally type <tt>make dist</tt>, irrespectively whether you have enabled a plugin build or not, which invokes the required build automatically.
116

edits

Navigation menu