Instructions for compiling gs5.50 for Debian 2.2r2, and for patching in
Samsung gdi driver.
Michael Conry Mon Mar 5 16:19:54 GMT 2001
First, unpack the gs5.50 archive. Unpacks into gs5.50/
copied the expanded jpeg,libpng,zlib archives into the directories
gs5.50/jpeg
gs5.50/libpng
gs5.50/zlib
directories respectively (these directories are named in the makefile, you
could change the makefile, or rename the directories).
cd into the gs5.50 directory (referred to as "." from now on)
Tried a make.
Make failed, with error relating to Xt, changed XLIBDIRS line of makefile as
follows (around line 260):
#XLIBDIRS=-L/usr/local/X/lib
#XLIBDIRS=-L/usr/lib/X11
XLIBDIRS=-L/usr/X11R6/lib/
(last one is the working one, first was original, second was my first
revision (changed this line after doing a find / -name '*Xt*' -print | less
and looking for likely candidates)).
The libXt.so* libraries are from packages:
xlib6g-dev: /usr/X11R6/lib/libXt.so
xlib6g: /usr/X11R6/lib/libXt.so.6
xlib6g: /usr/X11R6/lib/libXt.so.6.0
Respectively.
Also, changed line 243 as follows:
#XINCLUDE=-I/usr/local/X/include
XINCLUDE=-I/usr/X11R6/include
(first is orig, next is my version)
Tried make again,
This gives a good compile.
For gdi:
Copied the patch file into the gs5.50 directory and ran:
patch --verbose -p 1 -i ghostscript-5.50-secgdi.patch
The patch file failed to patch the unix-gcc.mak makefile, but did work on
devs.mak
I added "gdi.dev" to the end of line "DEVICE_DEVS3= etc.,"
tried make
Got error about missing arch.h, so set up a symbolic link to the file
ln -s ./obj/arch.h ./arch.h
Retried "make",
and it built OK now.
executable is in ./obj/gs
tried out the executable with the command
./obj/gs ./tiger.ps
(again from the build (gs5.50 directory), and got the nice tiger picture in
an x window).
./obj/gs --help | grep gdi gave me the output:
ljetplus ljet2p ljet3 ljet4 gdi cdeskjet cdjcolor cdjmono cdj550 pj pjxl
this indicates that the driver is installed.
(this gives a blank line on my own gs, which is unpatched)
This is enough to get you started, the trick is now to run
ghostscript with the gdi drive and the various flags, and to see if it gives
you good output. There will probably be a bit of fiddling in that, but i
again recommend
www.linuxprinting.org
as a good source of info