File: Build.ami

package info (click to toggle)
glhack 1.2-1
  • links: PTS
  • area: main
  • in suites: squeeze, wheezy
  • size: 24,604 kB
  • ctags: 18,992
  • sloc: ansic: 208,570; cpp: 13,139; yacc: 2,005; makefile: 1,161; lex: 377; sh: 321; awk: 89; sed: 11
file content (146 lines) | stat: -rw-r--r-- 7,212 bytes parent folder | download | duplicates (22)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146

                         Compiling Amiga NetHack 3.4
                Last Revision: 21 February 2002 for NetHack 3.4.2


   We would like to thank each and every one of the people who took
   the time and effort to report bugs to us.  THANK YOU!  (And keep
   up the good work!)

I. Introduction

    The Amiga-specific documentation has been split since the 3.1.3 release
    - please read the file Install.ami for information specific to the
    Amiga port before continuing.

    If you have problems with compilation, installation, or think you have
    found a bug in the game, please report it by electronic mail to the
    development group at nethack-bugs@nethack.org, where it will be routed
    to the appropriate person.  Include your configuration, the version of
    NetHack you are playing (use the 'v' command or see
    include/patchlevel.h), and as much specific information as possible.
    As NetHack runs on many different machines, be sure to mention that you
    are playing the Amiga version and also mention if you are using the
    version for mc68k or ppc.

    If you want to find out about distributing NetHack, read the license
    (in NetHack:license or type ?i during the game).

II. Compiling Amiga NetHack 3.4

II.A. Compilation Overview
    Compiling NetHack is not very hard - basically you do a little
    configuration and start make.  It does, however, require a good amount
    of disk space and time.  It also needs a good bit of memory, especially
    for linking.  

II.B. Basic Compilation

    NetHack can be built with SAS/C version 6.5x.  The commercial version
    of DICE might work, but NetHack version 3.2.2 or later haven't been
    compiled with it.  The "official" compiler for NetHack 3.4 is SAS/C 6.58
    - we have dropped support for SAS/C 5.x.

    The Manx/Aztec port has not been tested recently and is certainly
    broken.  Anyone managing to compile NetHack with this compiler is
    encouraged to submit context diffs of the required changes.  When last
    tested, NetHack required version 5.0B of that compiler.

    Compiling with gcc should also work.

II.B.1. Introduction to Compiling NetHack
    Before doing any compilation, read the README files distributed with
    the source.  These should familiarize you with the source tree layout
    and what files are shared with what computers; everything in the
    sys/amiga directory is used exclusively by the Amiga.

    The makefile (sys/amiga/Makefile.ami) depends on certain assignments,
    providing the developer with a fairly flexible environment.  See
    sys/amiga/Makefile.ami for assignment assumptions.  DICE users should
    see section II.B.3 for information on creating a DMakefile usable with
    DMake.

    Edit config.h to your liking and system configuration.  The defaults
    should be satisfactory for most systems.

    Read VERY CAREFULLY through the Makefile to familiarize yourself
    with which assignments are assumed.  Otherwise, you're going to get
    something like "Insert NH: in any drive."  You will need uudecode,
    and, if you need to modify dgn_comp or lev_comp, flex, and bison.
    The first thing Makefile.ami does is build makedefs, which handles
    a variety of data file generation, and then lev_comp and dgn_comp
    which compile the special levels.  Makedefs will then be run to create
    a few files, followed by a roughly alphabetically sorted compilation
    of the entire source tree.  This process will compile selected files
    from the sys/amiga, sys/share, win/tty, and src directories, eventually
    creating sbin/nethack.  After building the main binary, a make install
    will build the auxiliary files including help files, special levels,
    icons, and the font files and will put these files into their final
    positions - most will be in dlb archives (if DLB was defined in config.h).
    The first make run should be done in NH:obj and the make install should be
    done in NetHack:; for both runs, the makefile is NH:sys/amiga/Makefile.ami
    (or NH:sys/amiga/DMakefile for DMake and NH:sys/amiga/Makefile.agc for
    gcc).

    Note that not all the source is simple C code.  If you are modifying
    lev_comp or dgn_comp you may need bison and/or flex (depending on what
    modifications you are making).  You do not need any of these tools to
    simply build NetHack - all the C output files are provided in the source
    distribution.  Also, the ifchange script requires a version of diff that
    produces standard Unix format context diffs for proper operation - the
    version shipped with SAS/C is not sufficient.

    If you do not have bison and flex, copy the files from sys/share.  The
    include files go in include/ and the C files go in util/.  If the compile
    fails due to prototype errors for malloc and realloc, try deleting
    the first line of lev_comp.c and dgn_comp.c.

II.B.2. Compiling NetHack with SAS/C version 6.58

    NOTE WELL - Amiga NetHack has dropped support for SAS/C version 5.
    This version of NetHack was developed with SAS/C 6.58.  Earlier versions
    than version of the compiler are known to cause problems - don't use them.

    A couple of notes and warnings from the SAS/C users on the team:

	* Included in the SAS/C port is code for generating a SnapShot.tb
	  file upon catching various internal disasters.  That is why the
	  debug=l flag is in the makefile.  This adds about 270K to the disk
	  image, but it does not increase the run time memory requirements.

	* The 5.10b optimizer did not produce correct code for NetHack.  The
	  current optimizer has not been tested.

II.B.3.	Compiling NetHack with the commercial version of DICE

    IMPORTANT NOTE: If you are using DMake, you need to create DMakefile
    from Makefile.ami.  Do the following:

	cd NH:sys/amiga
	edit from Makefile.ami to DMakefile with mkdmake opt w255

    Some versions of DMake have been known to crash horribly on the
    makefile - if this happens, you'll need to download another make
    utility, such as AMake (ftp://ftp.dragonfire.net/amiga/utils/amake),
    which will run in DMake-compatibility mode if invoked with the -C switch
    (e.g. "amake -C -f NH:sys/amiga/DMakefile", or just
    "alias dmake amake -C").

    SECOND IMPORTANT NOTE: The score list is currently disabled when
    compiling under DICE, due to an as-yet-unknown problem which causes
    system crashes when displaying the score list.

    NetHack can be compiled using the commercial version of DICE only.  The
    registered shareware version had a bug in it which resulted in odd-
    aligned procedures.  (It is possible to patch DC1 to fix this problem;
    however, this is not recommended, and you should upgrade to the
    commercial version.)

    DICE 3.0 (the first commercial release) has a couple of bugs in it which
    turn up in several of the NetHack sources; the DCC30_BUG define fixes
    them.  If you have a more recent version of the compiler, you may be
    able to compile without this (and get slightly more efficient code) by
    commenting out the define in amiconf.h.

    During compilation, DICE will output a lot of warnings; they can be
    safely ignored.