zxcc v0.5.2

zxcc is a wrapper for the Hi-Tech C CP/M compiler, allowing it to be used as a cross-compiler under UNIX. Version 0.5.0 also works with the build tools necessary to assemble CP/M 3 (MAC, RMAC, LINK, GENCOM).

New in this version:

Compiles on boxes where sync() does not return int (reported by multiple users).
BDOS function 10 takes a pointer to unsigned char, thus allowing input buffers longer than 128 bytes (Andy Parkins)

Setting up

Firstly, build the compiler. It should not be necessary to rebuild bios.bin; but if you have to, it assembles using the z80asm assembler (part of the z80pack emulation package which can be found on the Walnut Creek CP/M CDROM) or the ZMAC assembler (downloadable from <http://www.nenie.org/cpcip/index.html#zmac>).

Previous versions of ZXCC could be compiled under DOS using DJGPP; this may still be possible, but has not been tested since the build system was changed to use the GNU autotools.

This version of zxcc contains copies of the CPMIO and CPMREDIR libraries, so you won't need to obtain them separately.

You will need the tools you want to use; either the Hi-Tech C compiler for CP/M <http://www.hitech.com.au> or Digital Research's tools at <http://www.cpm.z80.de> Once you have obtained the tools, documentation and possibly the library source, you need to decide where to put the files. zxcc uses three directories:

BINDIR80 (by default, /usr/local/lib/cpm/bin80) holds the compiler itself. You should copy the compiler .com files (or MAC, RMAC etc.) and bios.bin to this directory.
LIBDIR80 (by default, /usr/local/lib/cpm/lib80) holds the C libraries libc.lib, libf.lib, crtcpm.obj and rrtcpm.obj.
INCDIR80 (by default, /usr/local/lib/cpm/include80) holds the compiler .h files.

The locations of these directories are normally set by the configure script; you can override them by editing zxcc.h and uncommenting the lines that redefine them.

Once you have installed zxcc and the build tools, try building Hello World:

#include <stdio.h>
void main()
{
printf("Hello World\n");
}

or for RMAC:

CSEG LXI D,HELLO MVI C,9 CALL 5 RST 0 HELLO: DB 'Hello World',13,10,'$'

To compile the first example, type

zxc hello.c

; if all goes well, you should end up with a file called hello.com. You can test the resulting file by typing

zxcc hello.com

To assemble the second example, type

zxcc rmac.com hello
zxcc link.com hello

and run it as above. NOTE: RMAC requires that lines be terminated with CR/LF. You may need to put a unix2dos command in your makefile before you invoke RMAC.

Using zxcc

For detailed instructions, see the documentation for Hi-Tech C or the CP/M tools. zxcc behaves in the same way, but note the following points:

Program names

The names of the programs have been changed between CP/M and UNIX; for example, you would type

zxc hello.c

instead of

c hello.c

. The programs to use are:

zxc: The equivalent of C.COM.
zxas: The equivalent of ZAS.COM.
zxlink: The equivalent of LINK.COM.
zxlibr: The equivalent of LIBR.COM.

All these programs work by converting their arguments to a form suitable for zxcc, and then invoking zxcc.

There are no front-end programs for the CP/M build tools; you will have to enter arguments to these in the zxcc format given below.

Filenames

Where the documentation allows you to enter a CP/M filename, you should instead enter a UNIX one. The filename itself (as opposed to any directories in its path) must obey CP/M 8.3 naming conventions and be all lowercase.

Where the documentation requires a CP/M driveletter / user number

-I2:C:

you should enter a path complete with trailing slash:

-I/usr/src/linux-80/include/

Technical

zxcc emulates a subset of CP/M 3; hopefully enough to run the Hi-Tech C compiler. It can be used as a limited general-purpose CP/M 3 emulator provided the emulated program only uses a restricted subset of system calls.

zxcc behaves like the emulator com, allowing CP/M programs to be used transparently from a UNIX prompt. However com:

Emulates all of CP/M 2, rather than a subset of CP/M 3;
Is designed for general use, not tailored to Hi-Tech C;
Is written partly in assembly language and will only run on 68000-based computers;
Cannot map UNIX directories to CP/M drives;
Contains some bugs connected with command parsing and file I/O.

Syntax for zxcc is:

zxcc comfile.com arg1 arg2 ...

The comfile is the program to run; zxcc searches the current directory and BINDIR80 for it.

The arguments are parsed in this way:

Any argument starting with a - sign is passed to the CP/M program as-is, minus the leading - sign.
Any argument starting with a + sign is parsed as a filename (see below) and then concatenated to the previous argument.
Any argument starting "+-" is concatenated without being parsed.
All other arguments are parsed as filenames. The UNIX pathname is converted to a CP/M driveletter.

For example:

zxcc foo.com --Q -A /dev/null --I +/dev/zero +-, +/foo/bar

would pass these arguments to foo.com:

-Q A d:null -Id:zero,e:bar

The other programs are merely wrappers that convert their command lines into the form required by zxcc.

Errors

Any errors raised by the zxcc runtime system will be prefixed with zxcc:. Some errors you may encounter are:

Unsupported BDOS call: Part of CP/M 3 that the program uses has not been emulated. Add the required functionality to zxbdos.c and recompile.
Z80 encountered invalid trap: The CP/M program being run attempted to call the zxcc runtime system with an unknown call number. This will happen if the program was written for my emulator "Joyce".

Acknowledgements

Hi-Tech C was written by Hi-Tech Software.
The Z80 emulation engine was written by Ian Collier.
Thanks to Jacob Nevins, Andy Parkins and others for bug fix suggestions.

John Elliott, 28 March 2003