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
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
|
XZX
An X11-based ZX Spectrum emulator
by Erik Kunze <Erik.Kunze@fantasy.muc.de>
based on XZX 1.0.2 by Des Herriott
and many others
Overview
--------
XZX will run on most Unix systems, and by now most of the portability issues
have been sorted out. However, since I am developing XZX using Linux, you may
encounter problems from time to time. If this happens, let me know as soon as
possible so these can be fixed in the next release.
XZX is known to work on the following machines/operating systems:
Sparc - Solaris, SunOS 4.x, Linux, NetBSD
Intel - SVR4, SCO, SINIX, Linux, FreeBSD
Mips - SVR4, DEC Ultrix, SGI Irix, SINIX, Linux, NetBSD
IBM RS6000 - AIX v3.2.x
PA-RISC - HP/UX
DEC Alpha - OSF/1, Linux
Motorola 68K - Bull B.O.S., Linux
PowerPC - Linux
XZX will work with monochrome displays; contrasting colours are displayed with
the darker colour in black and the lighter colour in white, which works
reasonably well. Halftoning is used if the scaling factor is increased.
XZX was developed for Unix systems. Meanwhile, it has been ported to the
Windows 95/NT and Psion 3 environment.
If and when you succeed in getting XZX working on other platforms, please let
me know. Any diffs or descriptions of changes you made to make it work are
welcome.
Requirements
------------
These are the requirements for getting the Unix version to run:
o An X11R4 or newer server. R3 might work, but I have not tried it.
o The MIT-SHM extension is *strongly* recommended. It will work without it,
but will be SLOW.
o A 'C' compiler which supports prototypes. GCC works fine, although not in
strict ANSI mode (-ansi), since XZX uses some extensions.
o Lex/Yacc to compile the built-in debugger.
o Motif 1.2+ is required for the registered version of the emulator.
Installing
----------
To install the emulator, do the following:
o Unpack the archive to an appropriate directory.
o `cd' to the directory containing the package's source code and type
`./configure --enable-registered=[no|yes]' to configure the package for your
system. If you're using `csh' on an old version of System V, you might need
to type `sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some messages
telling which features it is checking for.
o Check the generated file "config.h" for some tweakable defines; descriptions
of what each definition does appear in these files. Check that proper
integer types are used for 8, 16 and 32 bit data on your platform.
o Type `make' to compile the package. Ignore warnings if you get them.
NOTE: z80.c takes quite a while to compile. If you run out of swapspace
try to undefine HAVE_ENOUGH_SWAP in "config.h".
o Type `make install' to install the programs and any data files and
documentation.
o You can test the emulator at this point by typing 'xzx'. This should start
Sinclair BASIC and give you the familiar "(c)1982 Sinclair Research Ltd"
message. If it does not, something is wrong.
o You can remove the program binaries and object files from the source code
directory by typing `make clean'. To also remove the files that `configure'
created (so you can compile the package for a different kind of computer),
type `make distclean'.
Compilers and Options
---------------------
Some systems require unusual options for compilation or linking that the
`configure' script does not know about. You can give `configure' initial
values for variables by setting them in the environment. Using a
Bourne-compatible shell, you can do that on the command line like this:
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
Installation Names
------------------
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an installation
prefix other than `/usr/local' by giving `configure' the option
`--prefix=PATH'.
You can specify separate installation prefixes for architecture-specific files
and architecture-independent files. If you give `configure' the option
`--exec-prefix=PATH', the package will use PATH as the prefix for installing
programs and libraries. Documentation and other data files will still use the
regular prefix.
In addition, if you use an unusual directory layout you can give options like
`--bindir=PATH' to specify different values for particular kinds of files. Run
`configure --help' for a list of the directories you can set and what kinds of
files go in them.
If the package supports it, you can cause programs to be installed with an
extra prefix or suffix on their names by giving `configure' the option
`--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
-----------------
XZX pays attention to `--enable-FEATURE' and `--with-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
For packages that use the X Window System, `configure' can usually find the X
include and library files automatically, but if it doesn't, you can use the
`configure' options `--x-includes=DIR' and `--x-libraries=DIR' to specify their
locations.
Specifying the System Type
--------------------------
There may be some features `configure' can not figure out automatically, but
needs to determine by the type of host the package will run on. Usually
`configure' can figure that out, but if it prints a message saying it can not
guess the host type, give it the `--host=TYPE' option. TYPE can either be a
short name for the system type, such as `sun4', or a canonical name with three
fields:
CPU-COMPANY-SYSTEM
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't need to
know the host type.
Operation Controls
------------------
`configure' recognizes the following options to control how it operates.
`--cache-file=FILE'
Use and save the results of the tests in FILE instead of `./config.cache'.
Set FILE to `/dev/null' to disable caching, for debugging `configure'.
`--help'
Print a summary of the options to `configure', and exit.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made. To suppress all
normal output, redirect it to `/dev/null' (any error messages will still be
shown).
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually `configure' can
determine that directory automatically.
`--version'
Print the version of Autoconf used to generate the `configure' script, and
exit.
`configure' also accepts some other, not widely useful, options.
|
