atari email archive

a collection of messages sent at Atari from 1983 to 1992.

New sound-call symbol file: AUDIO.DEF

(1 / 1)


	In addition to producing various header and equate files that contain
sound call symbols (AUDIO.H, AUDIO.ASM, AUDIO.OL, AUDIOE.H and AUDIOE.ASM) we
are now producing a generic file called:  AUDIO.DEF.   This is an attempt to
give you a symbol file that is generic enough for you to use in any imaginable
scenario.

This file is in the format:

 SOUNDCALL S_ABORT,102
 SOUNDCALL S_ADDCOINS,103

    ...etc...

	For your convenience, Mike Albaugh has created a number of files that
contain macros to aid in the massaging of AUDIO.DEF files. They live in 
EE$USERDISK:[68K_US.AUDIO] and are:

AUDEH_PP.MAC	To produce audioe.h, by doing:
	MACPP /out=audioe.h audeh_pp.mac

AUD_H_PP.MAC	To produce audio.h, by doing:
	MACPP /out=audio.h aud_h_pp.mac

AUDIO.ASM	To create audio.ol, assembled by ASM68 (or other MOTOROLA
	assembler)

AUDIO.MAC	To create audio.ol, assembled by MAC68K:
	MAC68K /NOBIN AUDIO.MAC

	Those who prefer binary object files can leave off the /NOBIN and get
	an audio.ob file.

AUDIOE.ASM	for inclusion in ASM68 assemblies, to "XREF" the symbols
	(for those who _do_ link to audio.ol or audio.ob)

AUDIOE.MAC	for inclusion in ASM68 assemblies, to "XREF" the symbols
	(for those who _do_ link to audio.ol or audio.ob)

AUD_SYM.ASM	for inclusion in ASM68 assemblies, to simply define the
	symbols (for those who do _not_ link to audio.ol, but re-assemble)

AUD_SYM.MAC	for inclusion in MAC68K assemblies, to simply define the
	symbols (for those who do _not_ link to audio.ol, but re-assemble)

	All these files "include audio.def", which may or may not be
what you want. On the one hand it makes the assembly command simpler,
which is a real plus for those using archaic command files that choke
on anything more complex than a single file name. On the other hand, some
MOTOROLA assemblers may choke if an "include" file also does an "include".
On yet another hand, none of these files are very big, so they could just
be snarfed and pasted...

	If you have comments to this approach please don't hesitate to contact
us.  Your suggestions might (and probably will) help the rest.

- brad -
Message 1 of 1

Jul 17, 1991