home *** CD-ROM | disk | FTP | other *** search
- Short: Ghostscript3.53 port with Amiga driver & no ixemul.library
- Author: GS(Aladdin)/Amiga(Olaf Barthel)/Port(me)
- Uploader: Joop.vandeWege@Medew.ENTO.WAU.NL
- Type: gfx/show
-
- This is the Amiga port of Ghostscript3.53. Ghostscript is a Postscript
- interpreter with support for Level 2 PS and PDF. This release includes
- *only* the Amiga display driver and the fileformat PNG. This is only a
- *small* part of the available device drivers and is a trade off between
- size and usability. The source is available from the same place you got
- the binary (is it?) so you can recompile to fit it to your needs.
-
- This port requires:
- - An Amiga equipped with an mc68000 CPU or any successor CPU model and
- Kickstart 2.04 or higher.
- - Approx. 4.7 MBytes of hard disk space available.
- - A minimum of 1 MByte of chip memory, depending on what you will want to
- do with the interpreter. Printer output requires at least 2 MBytes of
- contiguous memory (any memory, not necessarily chip memory).
- - A bunch of Postscript/Ghostscript fonts.
-
- Comments/Suggestions/Bugs to:
- Joop.vandeWege@medew.ento.wau.nl
- Please use a Subject field with the name 'GS353' in it.
- Please direct all mail to me except when you're 100% sure it is a GS
- problem then you can use the Aladdin email address.
-
- Joop van de Wege
-
-
- Getting Ghostscript.
- Download the binary archive, gs353bin.lha
- It contains all needed data in one directory with two versions of
- Ghostscript353 (GS), a mc68000 version and a version which should work
- on machines with an mc68020 and higher. It doesn't use the FPU
- (68881/2/68040) instructions.
- This one should run on plain A1200, A3000, A4000-030, A4000 and any
- A500/A600/A1000/A2000 machine with a mc68020/30/40/60 installed and enough
- RAM. On my machine (A3000 + Merlin) it uses 150Kb Chip and 1.5Mb Fast.
- Expect it to use more if the psfile is big/complex or when displaying PDF
- files and when using 256color modes for the Workbench.
-
- How to use Ghostscript.
- Unpack the archive gs353bin.lha to a suitable HD with enough room (~3.5M).
- A directory 'Ghostscript' will be created and all files needed are found
- within this directory.
- There are two ways to proceed from here.
- - Assign Ghostscript: to the directory where you unpacked the archive.
- Example: unpack on 'Work:', creates Work:Ghostscript
- Assign Ghostscript: Work:Ghostscript
- path Ghostscript: add
- (Optionally, remove one of the files gs000 or gs020-40sf and rename the
- remaining to 'gs')
- Now you can call 'gs' from anywhere with or without arguments. If you add
- the above fragment (Assign ... add) to your s:user-startup then it will
- available everytime you start your computer
- - Set the following environment variables:
- - GS_LIB, example: setenv GS_LIB=work:ghostscript/data
- - GS_DEVICE example: setenv GS_DEVICE=amiga (default)
- - GS_FONTPATH example: setenv GS_FONTPATH=work:ghostscript/fonts
- - GS_OPTIONS example: setenv GS_OPTIONS="-sDEVICE=png16m -r120"
- The only required variable is GS_LIB. Now you can copy 'GS' to a place
- which is in the AmigaDOS search path.
-
- See the 'Ghostscript/docs' directory for more information, like commandline
- options. Some notes:
- Watch out for case sensitivity when using commandline options, -sOutputFile
- is not equal to -soutputfile !!!!!
- Some very useful commandlines with comments in ():
- gs -h (outputs small help on most important arguments)
- gs (gs opens window on WB and use its palette, use 256color WB if possible)
- gs -sDEVICE=png16m (uses the built-in PNG support instead of window on WB)
- gs -sOutputFile=ram:output%02d.png -sDEVICE=png256
- (output to files numbered ram:output01.png/ram:output02.png/etc using
- the PNG format (8bit))
- gs -r120 (use 120dpi as resolution instead of built-in 72, uses heaps of
- memory at high values)
- Arguments useful for PDF files (and ps documents conforming to DSC ?)
- gs -dFirstPage=pagenumber (starts on the given page of the document)
- gs -dLastPage=pagenumber (Stops after the given page of the document)
- See use.doc/Switches for a complete overview of what is available.
-
- Recompiling GS:
- Steps needed to be done to recompile GS from scratch using GCC2.63/2.70:
- Get gs353src.lha
- Get gs353amiga.lha
- Get gs353jpeg6.lha
- Get gs353zlib.lha
- Get gs353png.lha
-
- Unpack gs353src to HD, a directory 'gs3.53' will be created.
- Unpack *in* this directory:
- - gs353amiga.lha, overwriting some files. This is OK
- gs353amiga.lha contains:
- - gdevamiga.c, the amiga device driver from Olaf Barthel
- - gdevpipe.c, patched for use with Libnix
- - gdevpng.c, bugfixed PNG device driver
- - geninit.c, bugfixed geninit
- - gp_amiga.c, platform dependant stuff for the Amiga
- - gsmisc.c, fixed wrong external declaration
- - makefile, how to recreate GS (this distribution rebuilds in the
- source directory, the upcoming ADE (Fred Fish) one will have a
- configure script)
-
- - gs353jpeg6 which creates the 'jpeg-6' directory
- - gs353zlib which creates the 'zlib' directory
- - gs353png which creates the 'pnglib' directory
- The last two archives are not needed when you don't intend to rebuild GS
- with PNG support.
- Edit the makefile and activate/deactivate the devices you want or adjust
- the paths. Read the comments in the makefile for directions.
- cd to drive:gs3.53 and type 'make' followed by 'make install'
- If you haven't forgotten to set the stack to a reasonable amount (~50K),
- you can sit back and have a cup of coffee. On my A3000 it takes about 2.5h
- to compile with the current device driver set and the file 'gdevamiga.c'
- needs about 7-8Mb when -O2 is on. It needs less if you don't optimize :)
- Make itself takes another 2Mb so in case of problems just compile
- gdevamiga.c on its own and let make resume after that. GCC2.7.0 (Aminet)
- works with VMM3.3 (on Aminet too).
-