3 Refer to the appropriate INSTALL files for your build system:
5 INSTALL.unix All UNIX builds, including cygwin
6 INSTALL.win32 Microsoft Visual C++ builds
7 INSTALL.dos WATCOM C/C++ builds
9 Appendix to 'INSTALL.dos':
10 --------------------------
11 The build instructions of the WATCOM build are generic and generated
12 automatically. They assume that the main Makefile would be called 'Makefile'.
13 This isn't the case for AdPlug's WATCOM build! AdPlug's WATCOM Makefile is
14 called 'Makefile.wat'. Thus, you have to give the commandline option
15 '/f Makefile.wat' every time you run a 'wmake' command. For example, to
16 install AdPlug, call wmake like this:
18 wmake /f Makefile.wat install
20 Do this similary with any other 'wmake' target.
24 If you checked out from CVS and use UNIX, first run:
28 to generate the build cruft and get the configure script. You need recent
29 versions of autoconf, automake and libtool to do this.
31 Also, you need to pass --enable-maintainer-mode to the configure script to
32 generate some missing files.
34 Extra setup for DOS and Windows builds:
35 ---------------------------------------
36 After you've done all steps from 'INSTALL.dos' or 'INSTALL.win32', you have
37 to copy the file 'binio.h.in' to 'binio.h' (maybe overwriting it) in the
38 'src' subdirectory and then open it ('binio.h'). Set all #define's in the
39 configuration section of the file to your preferred settings. All items are
42 Next, substitute the biggest (in size of bytes, as returned by the sizeof()
43 operator) standard integer and floating-point types for @TYPE_INT@ and
44 @TYPE_FLOAT@, respectively. Most of the time, you would just substitute 'long'
45 for @TYPE_INT@ and 'double' for @TYPE_FLOAT@, but some compilers have even
46 longer types, like 'long long' and 'long double'. If your compiler supports one
47 of those, you can substitute them instead to be able to access even longer
48 sections within your binary streams.