1998-04-19 18:34:52 +00:00
|
|
|
--- unix-gcc.mak.orig Tue Nov 25 03:29:01 1997
|
- Update the additional hp850 driver to newest release 1.3
- Since the author decided to put a version number into his archive,
we can now safely fetch the file from his site.
- patch-ad is useless now
- updated the configure and configure.batch script, to show all possible
drivers
- install hp850 drivers license and readme file in the gs doc dir
- update the DESCR file, mention the two add on packages in this port
- The new driver supports the following additional printers:
Support for HP DeskJet 670, 690, 850, 855, 870, 890, 1100 and 1600,
See announcement on http://bonk.ethz.ch/hp850/hp850.html
Please note, that some of the drivers have certain restrictions
and produce huge output files ... Please read the release notes !!!
The author makes suggestions on his website, what driver to choose
if you need a fast printout, see
http://bonk.ethz.ch/hp850/hp850-readme.1.3.html
1998-06-04 20:11:39 +00:00
|
|
|
+++ unix-gcc.mak Thu Jun 4 21:44:45 1998
|
1998-04-19 18:34:52 +00:00
|
|
|
@@ -130,7 +130,7 @@
|
|
|
|
|
# You may need to change this if the IJG library version changes.
|
|
|
|
|
# See jpeg.mak for more information.
|
|
|
|
|
|
|
|
|
|
-JSRCDIR=jpeg-6a
|
|
|
|
|
+JSRCDIR=jpeg-6b
|
|
|
|
|
JVERSION=6
|
|
|
|
|
|
|
|
|
|
# Define the directory where the PNG library sources are stored,
|
|
|
|
|
@@ -151,7 +151,7 @@
|
Major cleanup for ghostscript5 port.
- merged patch-af into patch-aa, both patches hacked unix-gcc.mak
- merged the scripts/{configure,configure.batch} changes into
patch-aa, so that unix-gcc.mak is hacked only by patch-aa
- when doing interactive configuration, every device driver is
now turned on, so you have to deselect devices
- when using BATCH compilation, you now get every supported device,
this one is especially for Satoshi, when making gs packages !
- Added a note into unix-gcc.mak, that DEVICE_DEVS now completely
are removed in the makefile, instead of this, the two configure
scripts now completely control, which devices have to be compiled in.
So, the configure target "patches" the unix-gcc.mak Makefile and
puts a DEVICE_DEVS line at line 1. When doing batch compilation
every device is included in this line, or the wanted devices ...
- The compilation option -DA4 is now included if you compile the port
by saying "make A4=yes".
I hope, I didn't forget a driver, look at that long line ;-)
BTW, I didn't create that DEVICE_DEVS line by hand, I did the
interactive installation, which created it automatically, and
after that I "stealed" that DEVICE_DEVS line for inclusion
into configure.batch ;-) So the devices in configure and configure.batch
are exactly the same, you only have to compare devices.mak with one
of the configure scripts.
BTW, should we nuke ghostscript4 ??? Does somebody know if any
port needs gs4 ???
1997-06-14 09:36:31 +00:00
|
|
|
# Define the directory where the zlib sources are stored.
|
|
|
|
|
# See zlib.mak for more information.
|
|
|
|
|
|
|
|
|
|
-ZSRCDIR=zlib
|
|
|
|
|
+ZSRCDIR=.
|
|
|
|
|
|
|
|
|
|
# Choose whether to use a shared version of the zlib library, and if so,
|
|
|
|
|
# what its name is (usually libz, but sometimes libgz).
|
1998-04-19 18:34:52 +00:00
|
|
|
@@ -176,7 +176,7 @@
|
Major cleanup for ghostscript5 port.
- merged patch-af into patch-aa, both patches hacked unix-gcc.mak
- merged the scripts/{configure,configure.batch} changes into
patch-aa, so that unix-gcc.mak is hacked only by patch-aa
- when doing interactive configuration, every device driver is
now turned on, so you have to deselect devices
- when using BATCH compilation, you now get every supported device,
this one is especially for Satoshi, when making gs packages !
- Added a note into unix-gcc.mak, that DEVICE_DEVS now completely
are removed in the makefile, instead of this, the two configure
scripts now completely control, which devices have to be compiled in.
So, the configure target "patches" the unix-gcc.mak Makefile and
puts a DEVICE_DEVS line at line 1. When doing batch compilation
every device is included in this line, or the wanted devices ...
- The compilation option -DA4 is now included if you compile the port
by saying "make A4=yes".
I hope, I didn't forget a driver, look at that long line ;-)
BTW, I didn't create that DEVICE_DEVS line by hand, I did the
interactive installation, which created it automatically, and
after that I "stealed" that DEVICE_DEVS line for inclusion
into configure.batch ;-) So the devices in configure and configure.batch
are exactly the same, you only have to compare devices.mak with one
of the configure scripts.
BTW, should we nuke ghostscript4 ??? Does somebody know if any
port needs gs4 ???
1997-06-14 09:36:31 +00:00
|
|
|
|
|
|
|
|
# Define the name of the C compiler.
|
|
|
|
|
|
|
|
|
|
-CC=gcc
|
|
|
|
|
+CC=cc
|
|
|
|
|
|
|
|
|
|
# Define the name of the linker for the final link step.
|
|
|
|
|
# Normally this is the same as the C compiler.
|
1998-04-19 18:34:52 +00:00
|
|
|
@@ -218,7 +218,7 @@
|
1997-06-11 06:20:47 +00:00
|
|
|
# SVR4 may need -lnsl.
|
|
|
|
|
# (Libraries required by individual drivers are handled automatically.)
|
|
|
|
|
|
|
|
|
|
-EXTRALIBS=
|
|
|
|
|
+EXTRALIBS=-lz
|
|
|
|
|
|
|
|
|
|
# Define the include switch(es) for the X11 header files.
|
|
|
|
|
# This can be null if handled in some other way (e.g., the files are
|
1998-04-19 18:34:52 +00:00
|
|
|
@@ -228,7 +228,7 @@
|
Major cleanup for ghostscript5 port.
- merged patch-af into patch-aa, both patches hacked unix-gcc.mak
- merged the scripts/{configure,configure.batch} changes into
patch-aa, so that unix-gcc.mak is hacked only by patch-aa
- when doing interactive configuration, every device driver is
now turned on, so you have to deselect devices
- when using BATCH compilation, you now get every supported device,
this one is especially for Satoshi, when making gs packages !
- Added a note into unix-gcc.mak, that DEVICE_DEVS now completely
are removed in the makefile, instead of this, the two configure
scripts now completely control, which devices have to be compiled in.
So, the configure target "patches" the unix-gcc.mak Makefile and
puts a DEVICE_DEVS line at line 1. When doing batch compilation
every device is included in this line, or the wanted devices ...
- The compilation option -DA4 is now included if you compile the port
by saying "make A4=yes".
I hope, I didn't forget a driver, look at that long line ;-)
BTW, I didn't create that DEVICE_DEVS line by hand, I did the
interactive installation, which created it automatically, and
after that I "stealed" that DEVICE_DEVS line for inclusion
into configure.batch ;-) So the devices in configure and configure.batch
are exactly the same, you only have to compare devices.mak with one
of the configure scripts.
BTW, should we nuke ghostscript4 ??? Does somebody know if any
port needs gs4 ???
1997-06-14 09:36:31 +00:00
|
|
|
# Note that x_.h expects to find the header files in $(XINCLUDE)/X11,
|
|
|
|
|
# not in $(XINCLUDE).
|
|
|
|
|
|
|
|
|
|
-XINCLUDE=-I/usr/local/X/include
|
|
|
|
|
+XINCLUDE=-I/usr/X11R6/include
|
|
|
|
|
|
|
|
|
|
# Define the directory/ies and library names for the X11 library files.
|
|
|
|
|
# XLIBDIRS is for ld and should include -L; XLIBDIR is for LD_RUN_PATH
|
1998-04-19 18:34:52 +00:00
|
|
|
@@ -243,7 +243,7 @@
|
Major cleanup for ghostscript5 port.
- merged patch-af into patch-aa, both patches hacked unix-gcc.mak
- merged the scripts/{configure,configure.batch} changes into
patch-aa, so that unix-gcc.mak is hacked only by patch-aa
- when doing interactive configuration, every device driver is
now turned on, so you have to deselect devices
- when using BATCH compilation, you now get every supported device,
this one is especially for Satoshi, when making gs packages !
- Added a note into unix-gcc.mak, that DEVICE_DEVS now completely
are removed in the makefile, instead of this, the two configure
scripts now completely control, which devices have to be compiled in.
So, the configure target "patches" the unix-gcc.mak Makefile and
puts a DEVICE_DEVS line at line 1. When doing batch compilation
every device is included in this line, or the wanted devices ...
- The compilation option -DA4 is now included if you compile the port
by saying "make A4=yes".
I hope, I didn't forget a driver, look at that long line ;-)
BTW, I didn't create that DEVICE_DEVS line by hand, I did the
interactive installation, which created it automatically, and
after that I "stealed" that DEVICE_DEVS line for inclusion
into configure.batch ;-) So the devices in configure and configure.batch
are exactly the same, you only have to compare devices.mak with one
of the configure scripts.
BTW, should we nuke ghostscript4 ??? Does somebody know if any
port needs gs4 ???
1997-06-14 09:36:31 +00:00
|
|
|
#XLIBS=Xt SM ICE Xext X11
|
|
|
|
|
|
|
|
|
|
#XLIBDIRS=-L/usr/local/X/lib
|
|
|
|
|
-XLIBDIRS=-L/usr/X11/lib
|
1998-09-12 17:40:07 +00:00
|
|
|
-XLIBDIR=
|
Major cleanup for ghostscript5 port.
- merged patch-af into patch-aa, both patches hacked unix-gcc.mak
- merged the scripts/{configure,configure.batch} changes into
patch-aa, so that unix-gcc.mak is hacked only by patch-aa
- when doing interactive configuration, every device driver is
now turned on, so you have to deselect devices
- when using BATCH compilation, you now get every supported device,
this one is especially for Satoshi, when making gs packages !
- Added a note into unix-gcc.mak, that DEVICE_DEVS now completely
are removed in the makefile, instead of this, the two configure
scripts now completely control, which devices have to be compiled in.
So, the configure target "patches" the unix-gcc.mak Makefile and
puts a DEVICE_DEVS line at line 1. When doing batch compilation
every device is included in this line, or the wanted devices ...
- The compilation option -DA4 is now included if you compile the port
by saying "make A4=yes".
I hope, I didn't forget a driver, look at that long line ;-)
BTW, I didn't create that DEVICE_DEVS line by hand, I did the
interactive installation, which created it automatically, and
after that I "stealed" that DEVICE_DEVS line for inclusion
into configure.batch ;-) So the devices in configure and configure.batch
are exactly the same, you only have to compare devices.mak with one
of the configure scripts.
BTW, should we nuke ghostscript4 ??? Does somebody know if any
port needs gs4 ???
1997-06-14 09:36:31 +00:00
|
|
|
+XLIBDIRS=-L/usr/X11R6/lib
|
1998-09-12 17:40:07 +00:00
|
|
|
+XLIBDIR=/usr/X11R6/lib
|
Major cleanup for ghostscript5 port.
- merged patch-af into patch-aa, both patches hacked unix-gcc.mak
- merged the scripts/{configure,configure.batch} changes into
patch-aa, so that unix-gcc.mak is hacked only by patch-aa
- when doing interactive configuration, every device driver is
now turned on, so you have to deselect devices
- when using BATCH compilation, you now get every supported device,
this one is especially for Satoshi, when making gs packages !
- Added a note into unix-gcc.mak, that DEVICE_DEVS now completely
are removed in the makefile, instead of this, the two configure
scripts now completely control, which devices have to be compiled in.
So, the configure target "patches" the unix-gcc.mak Makefile and
puts a DEVICE_DEVS line at line 1. When doing batch compilation
every device is included in this line, or the wanted devices ...
- The compilation option -DA4 is now included if you compile the port
by saying "make A4=yes".
I hope, I didn't forget a driver, look at that long line ;-)
BTW, I didn't create that DEVICE_DEVS line by hand, I did the
interactive installation, which created it automatically, and
after that I "stealed" that DEVICE_DEVS line for inclusion
into configure.batch ;-) So the devices in configure and configure.batch
are exactly the same, you only have to compare devices.mak with one
of the configure scripts.
BTW, should we nuke ghostscript4 ??? Does somebody know if any
port needs gs4 ???
1997-06-14 09:36:31 +00:00
|
|
|
XLIBS=Xt Xext X11
|
|
|
|
|
|
1998-04-19 18:34:52 +00:00
|
|
|
@@ -287,22 +287,22 @@
|
Major cleanup for ghostscript5 port.
- merged patch-af into patch-aa, both patches hacked unix-gcc.mak
- merged the scripts/{configure,configure.batch} changes into
patch-aa, so that unix-gcc.mak is hacked only by patch-aa
- when doing interactive configuration, every device driver is
now turned on, so you have to deselect devices
- when using BATCH compilation, you now get every supported device,
this one is especially for Satoshi, when making gs packages !
- Added a note into unix-gcc.mak, that DEVICE_DEVS now completely
are removed in the makefile, instead of this, the two configure
scripts now completely control, which devices have to be compiled in.
So, the configure target "patches" the unix-gcc.mak Makefile and
puts a DEVICE_DEVS line at line 1. When doing batch compilation
every device is included in this line, or the wanted devices ...
- The compilation option -DA4 is now included if you compile the port
by saying "make A4=yes".
I hope, I didn't forget a driver, look at that long line ;-)
BTW, I didn't create that DEVICE_DEVS line by hand, I did the
interactive installation, which created it automatically, and
after that I "stealed" that DEVICE_DEVS line for inclusion
into configure.batch ;-) So the devices in configure and configure.batch
are exactly the same, you only have to compare devices.mak with one
of the configure scripts.
BTW, should we nuke ghostscript4 ??? Does somebody know if any
port needs gs4 ???
1997-06-14 09:36:31 +00:00
|
|
|
|
1997-08-24 14:36:26 +00:00
|
|
|
# Choose the device(s) to include. See devs.mak for details.
|
Major cleanup for ghostscript5 port.
- merged patch-af into patch-aa, both patches hacked unix-gcc.mak
- merged the scripts/{configure,configure.batch} changes into
patch-aa, so that unix-gcc.mak is hacked only by patch-aa
- when doing interactive configuration, every device driver is
now turned on, so you have to deselect devices
- when using BATCH compilation, you now get every supported device,
this one is especially for Satoshi, when making gs packages !
- Added a note into unix-gcc.mak, that DEVICE_DEVS now completely
are removed in the makefile, instead of this, the two configure
scripts now completely control, which devices have to be compiled in.
So, the configure target "patches" the unix-gcc.mak Makefile and
puts a DEVICE_DEVS line at line 1. When doing batch compilation
every device is included in this line, or the wanted devices ...
- The compilation option -DA4 is now included if you compile the port
by saying "make A4=yes".
I hope, I didn't forget a driver, look at that long line ;-)
BTW, I didn't create that DEVICE_DEVS line by hand, I did the
interactive installation, which created it automatically, and
after that I "stealed" that DEVICE_DEVS line for inclusion
into configure.batch ;-) So the devices in configure and configure.batch
are exactly the same, you only have to compare devices.mak with one
of the configure scripts.
BTW, should we nuke ghostscript4 ??? Does somebody know if any
port needs gs4 ???
1997-06-14 09:36:31 +00:00
|
|
|
|
|
|
|
|
-DEVICE_DEVS=x11.dev x11alpha.dev x11cmyk.dev x11gray2.dev x11mono.dev
|
|
|
|
|
-DEVICE_DEVS1=
|
|
|
|
|
-DEVICE_DEVS2=
|
|
|
|
|
-DEVICE_DEVS3=deskjet.dev djet500.dev laserjet.dev ljetplus.dev ljet2p.dev ljet3.dev ljet4.dev
|
|
|
|
|
-DEVICE_DEVS4=cdeskjet.dev cdjcolor.dev cdjmono.dev cdj550.dev pj.dev pjxl.dev pjxl300.dev
|
1997-08-24 14:36:26 +00:00
|
|
|
-DEVICE_DEVS5=uniprint.dev
|
Major cleanup for ghostscript5 port.
- merged patch-af into patch-aa, both patches hacked unix-gcc.mak
- merged the scripts/{configure,configure.batch} changes into
patch-aa, so that unix-gcc.mak is hacked only by patch-aa
- when doing interactive configuration, every device driver is
now turned on, so you have to deselect devices
- when using BATCH compilation, you now get every supported device,
this one is especially for Satoshi, when making gs packages !
- Added a note into unix-gcc.mak, that DEVICE_DEVS now completely
are removed in the makefile, instead of this, the two configure
scripts now completely control, which devices have to be compiled in.
So, the configure target "patches" the unix-gcc.mak Makefile and
puts a DEVICE_DEVS line at line 1. When doing batch compilation
every device is included in this line, or the wanted devices ...
- The compilation option -DA4 is now included if you compile the port
by saying "make A4=yes".
I hope, I didn't forget a driver, look at that long line ;-)
BTW, I didn't create that DEVICE_DEVS line by hand, I did the
interactive installation, which created it automatically, and
after that I "stealed" that DEVICE_DEVS line for inclusion
into configure.batch ;-) So the devices in configure and configure.batch
are exactly the same, you only have to compare devices.mak with one
of the configure scripts.
BTW, should we nuke ghostscript4 ??? Does somebody know if any
port needs gs4 ???
1997-06-14 09:36:31 +00:00
|
|
|
-DEVICE_DEVS6=bj10e.dev bj200.dev bjc600.dev bjc800.dev
|
|
|
|
|
-DEVICE_DEVS7=faxg3.dev faxg32d.dev faxg4.dev
|
|
|
|
|
-DEVICE_DEVS8=pcxmono.dev pcxgray.dev pcx16.dev pcx256.dev pcx24b.dev pcxcmyk.dev
|
|
|
|
|
-DEVICE_DEVS9=pbm.dev pbmraw.dev pgm.dev pgmraw.dev pgnm.dev pgnmraw.dev pnm.dev pnmraw.dev ppm.dev ppmraw.dev
|
|
|
|
|
-DEVICE_DEVS10=tiffcrle.dev tiffg3.dev tiffg32d.dev tiffg4.dev tifflzw.dev tiffpack.dev
|
|
|
|
|
-DEVICE_DEVS11=tiff12nc.dev tiff24nc.dev
|
|
|
|
|
-DEVICE_DEVS12=psmono.dev psgray.dev bit.dev bitrgb.dev bitcmyk.dev
|
|
|
|
|
-DEVICE_DEVS13=pngmono.dev pnggray.dev png16.dev png256.dev png16m.dev
|
|
|
|
|
-DEVICE_DEVS14=jpeg.dev jpeggray.dev
|
|
|
|
|
-DEVICE_DEVS15=pdfwrite.dev pswrite.dev epswrite.dev pxlmono.dev pxlcolor.dev
|
1997-08-24 14:36:26 +00:00
|
|
|
+#DEVICE_DEVS=x11.dev x11alpha.dev x11cmyk.dev x11gray2.dev x11mono.dev
|
|
|
|
|
+#DEVICE_DEVS1=
|
|
|
|
|
+#DEVICE_DEVS2=
|
|
|
|
|
+#DEVICE_DEVS3=deskjet.dev djet500.dev laserjet.dev ljetplus.dev ljet2p.dev ljet3.dev ljet4.dev
|
|
|
|
|
+#DEVICE_DEVS4=cdeskjet.dev cdjcolor.dev cdjmono.dev cdj550.dev pj.dev pjxl.dev pjxl300.dev
|
|
|
|
|
+#DEVICE_DEVS5=uniprint.dev
|
|
|
|
|
+#DEVICE_DEVS6=bj10e.dev bj200.dev bjc600.dev bjc800.dev
|
|
|
|
|
+#DEVICE_DEVS7=faxg3.dev faxg32d.dev faxg4.dev
|
|
|
|
|
+#DEVICE_DEVS8=pcxmono.dev pcxgray.dev pcx16.dev pcx256.dev pcx24b.dev pcxcmyk.dev
|
|
|
|
|
+#DEVICE_DEVS9=pbm.dev pbmraw.dev pgm.dev pgmraw.dev pgnm.dev pgnmraw.dev pnm.dev pnmraw.dev ppm.dev ppmraw.dev
|
|
|
|
|
+#DEVICE_DEVS10=tiffcrle.dev tiffg3.dev tiffg32d.dev tiffg4.dev tifflzw.dev tiffpack.dev
|
|
|
|
|
+#DEVICE_DEVS11=tiff12nc.dev tiff24nc.dev
|
|
|
|
|
+#DEVICE_DEVS12=psmono.dev psgray.dev bit.dev bitrgb.dev bitcmyk.dev
|
|
|
|
|
+#DEVICE_DEVS13=pngmono.dev pnggray.dev png16.dev png256.dev png16m.dev
|
|
|
|
|
+#DEVICE_DEVS14=jpeg.dev jpeggray.dev
|
|
|
|
|
+#DEVICE_DEVS15=pdfwrite.dev pswrite.dev epswrite.dev pxlmono.dev pxlcolor.dev
|
|
|
|
|
|
Major cleanup for ghostscript5 port.
- merged patch-af into patch-aa, both patches hacked unix-gcc.mak
- merged the scripts/{configure,configure.batch} changes into
patch-aa, so that unix-gcc.mak is hacked only by patch-aa
- when doing interactive configuration, every device driver is
now turned on, so you have to deselect devices
- when using BATCH compilation, you now get every supported device,
this one is especially for Satoshi, when making gs packages !
- Added a note into unix-gcc.mak, that DEVICE_DEVS now completely
are removed in the makefile, instead of this, the two configure
scripts now completely control, which devices have to be compiled in.
So, the configure target "patches" the unix-gcc.mak Makefile and
puts a DEVICE_DEVS line at line 1. When doing batch compilation
every device is included in this line, or the wanted devices ...
- The compilation option -DA4 is now included if you compile the port
by saying "make A4=yes".
I hope, I didn't forget a driver, look at that long line ;-)
BTW, I didn't create that DEVICE_DEVS line by hand, I did the
interactive installation, which created it automatically, and
after that I "stealed" that DEVICE_DEVS line for inclusion
into configure.batch ;-) So the devices in configure and configure.batch
are exactly the same, you only have to compare devices.mak with one
of the configure scripts.
BTW, should we nuke ghostscript4 ??? Does somebody know if any
port needs gs4 ???
1997-06-14 09:36:31 +00:00
|
|
|
# ---------------------------- End of options --------------------------- #
|
|
|
|
|
|
1998-04-19 18:34:52 +00:00
|
|
|
@@ -3676,8 +3676,8 @@
|
1997-08-24 14:36:26 +00:00
|
|
|
libpng95.dev: $(LIBPNG_MAK) $(ECHOGS_XE) pngwio.$(OBJ) crc32.dev
|
|
|
|
|
$(SETMOD) libpng95 pngwio.$(OBJ) -include crc32
|
|
|
|
|
|
|
|
|
|
-libpng96.dev: $(LIBPNG_MAK) $(ECHOGS_XE) pngwio.$(OBJ) crc32.dev
|
|
|
|
|
- $(SETMOD) libpng96 pngwio.$(OBJ) -include crc32
|
|
|
|
|
+libpng96.dev: $(LIBPNG_MAK) $(ECHOGS_XE) pngwio.$(OBJ)
|
|
|
|
|
+ $(SETMOD) libpng96 pngwio.$(OBJ)
|
|
|
|
|
# Copyright (C) 1995, 1996, 1997 Aladdin Enterprises. All rights reserved.
|
|
|
|
|
#
|
|
|
|
|
# This file is part of Aladdin Ghostscript.
|
1998-04-19 18:34:52 +00:00
|
|
|
@@ -3758,7 +3758,7 @@
|
Major cleanup for ghostscript5 port.
- merged patch-af into patch-aa, both patches hacked unix-gcc.mak
- merged the scripts/{configure,configure.batch} changes into
patch-aa, so that unix-gcc.mak is hacked only by patch-aa
- when doing interactive configuration, every device driver is
now turned on, so you have to deselect devices
- when using BATCH compilation, you now get every supported device,
this one is especially for Satoshi, when making gs packages !
- Added a note into unix-gcc.mak, that DEVICE_DEVS now completely
are removed in the makefile, instead of this, the two configure
scripts now completely control, which devices have to be compiled in.
So, the configure target "patches" the unix-gcc.mak Makefile and
puts a DEVICE_DEVS line at line 1. When doing batch compilation
every device is included in this line, or the wanted devices ...
- The compilation option -DA4 is now included if you compile the port
by saying "make A4=yes".
I hope, I didn't forget a driver, look at that long line ;-)
BTW, I didn't create that DEVICE_DEVS line by hand, I did the
interactive installation, which created it automatically, and
after that I "stealed" that DEVICE_DEVS line for inclusion
into configure.batch ;-) So the devices in configure and configure.batch
are exactly the same, you only have to compare devices.mak with one
of the configure scripts.
BTW, should we nuke ghostscript4 ??? Does somebody know if any
port needs gs4 ???
1997-06-14 09:36:31 +00:00
|
|
|
zlibe_1.dev: $(MAKEFILE) $(ZLIB_MAK) $(ECHOGS_XE)
|
|
|
|
|
$(SETMOD) zlibe_1 -lib $(ZLIB_NAME)
|
1997-06-11 06:20:47 +00:00
|
|
|
|
|
|
|
|
-zlibe_=adler32.$(OBJ) deflate.$(OBJ) trees.$(OBJ)
|
|
|
|
|
+zlibe_=
|
|
|
|
|
zlibe_0.dev: $(ZLIB_MAK) $(ECHOGS_XE) zlibc.dev $(zlibe_)
|
|
|
|
|
$(SETMOD) zlibe_0 $(zlibe_)
|
|
|
|
|
$(ADDMOD) zlibe_0 -include zlibc
|
1998-04-19 18:34:52 +00:00
|
|
|
@@ -3805,11 +3805,11 @@
|
1997-06-11 06:20:47 +00:00
|
|
|
|
|
|
|
|
zlibd1_=infblock.$(OBJ) infcodes.$(OBJ) inffast.$(OBJ)
|
|
|
|
|
zlibd2_=inflate.$(OBJ) inftrees.$(OBJ) infutil.$(OBJ)
|
|
|
|
|
-zlibd_ = $(zlibd1_) $(zlibd2_)
|
|
|
|
|
-zlibd_0.dev: $(ZLIB_MAK) $(ECHOGS_XE) zlibc.dev $(zlibd_)
|
|
|
|
|
- $(SETMOD) zlibd_0 $(zlibd1_)
|
|
|
|
|
- $(ADDMOD) zlibd_0 -obj $(zlibd2_)
|
|
|
|
|
- $(ADDMOD) zlibd_0 -include zlibc
|
|
|
|
|
+zlibd_ =
|
|
|
|
|
+zlibd_0.dev: $(ZLIB_MAK) $(ECHOGS_XE) zlibc.dev
|
|
|
|
|
+ $(SETMOD) zlibd_0
|
|
|
|
|
+ $(ADDMOD) zlibd_0
|
|
|
|
|
+ $(ADDMOD) zlibd_0
|
|
|
|
|
|
Major cleanup for ghostscript5 port.
- merged patch-af into patch-aa, both patches hacked unix-gcc.mak
- merged the scripts/{configure,configure.batch} changes into
patch-aa, so that unix-gcc.mak is hacked only by patch-aa
- when doing interactive configuration, every device driver is
now turned on, so you have to deselect devices
- when using BATCH compilation, you now get every supported device,
this one is especially for Satoshi, when making gs packages !
- Added a note into unix-gcc.mak, that DEVICE_DEVS now completely
are removed in the makefile, instead of this, the two configure
scripts now completely control, which devices have to be compiled in.
So, the configure target "patches" the unix-gcc.mak Makefile and
puts a DEVICE_DEVS line at line 1. When doing batch compilation
every device is included in this line, or the wanted devices ...
- The compilation option -DA4 is now included if you compile the port
by saying "make A4=yes".
I hope, I didn't forget a driver, look at that long line ;-)
BTW, I didn't create that DEVICE_DEVS line by hand, I did the
interactive installation, which created it automatically, and
after that I "stealed" that DEVICE_DEVS line for inclusion
into configure.batch ;-) So the devices in configure and configure.batch
are exactly the same, you only have to compare devices.mak with one
of the configure scripts.
BTW, should we nuke ghostscript4 ??? Does somebody know if any
port needs gs4 ???
1997-06-14 09:36:31 +00:00
|
|
|
infblock.$(OBJ): $(ZSRC)infblock.c $(ZDEP) zutil.h
|
|
|
|
|
$(CP_) $(ZSRC)infblock.c .
|
- Update the additional hp850 driver to newest release 1.3
- Since the author decided to put a version number into his archive,
we can now safely fetch the file from his site.
- patch-ad is useless now
- updated the configure and configure.batch script, to show all possible
drivers
- install hp850 drivers license and readme file in the gs doc dir
- update the DESCR file, mention the two add on packages in this port
- The new driver supports the following additional printers:
Support for HP DeskJet 670, 690, 850, 855, 870, 890, 1100 and 1600,
See announcement on http://bonk.ethz.ch/hp850/hp850.html
Please note, that some of the drivers have certain restrictions
and produce huge output files ... Please read the release notes !!!
The author makes suggestions on his website, what driver to choose
if you need a fast printout, see
http://bonk.ethz.ch/hp850/hp850-readme.1.3.html
1998-06-04 20:11:39 +00:00
|
|
|
@@ -4584,8 +4584,22 @@
|
Major cleanup for ghostscript5 port.
- merged patch-af into patch-aa, both patches hacked unix-gcc.mak
- merged the scripts/{configure,configure.batch} changes into
patch-aa, so that unix-gcc.mak is hacked only by patch-aa
- when doing interactive configuration, every device driver is
now turned on, so you have to deselect devices
- when using BATCH compilation, you now get every supported device,
this one is especially for Satoshi, when making gs packages !
- Added a note into unix-gcc.mak, that DEVICE_DEVS now completely
are removed in the makefile, instead of this, the two configure
scripts now completely control, which devices have to be compiled in.
So, the configure target "patches" the unix-gcc.mak Makefile and
puts a DEVICE_DEVS line at line 1. When doing batch compilation
every device is included in this line, or the wanted devices ...
- The compilation option -DA4 is now included if you compile the port
by saying "make A4=yes".
I hope, I didn't forget a driver, look at that long line ;-)
BTW, I didn't create that DEVICE_DEVS line by hand, I did the
interactive installation, which created it automatically, and
after that I "stealed" that DEVICE_DEVS line for inclusion
into configure.batch ;-) So the devices in configure and configure.batch
are exactly the same, you only have to compare devices.mak with one
of the configure scripts.
BTW, should we nuke ghostscript4 ??? Does somebody know if any
port needs gs4 ???
1997-06-14 09:36:31 +00:00
|
|
|
|
|
|
|
|
cdeskjet_=gdevcdj.$(OBJ) $(HPPCL)
|
|
|
|
|
|
|
|
|
|
+cdeskjet8_=gdevcd8.$(OBJ) $(HPPCL)
|
|
|
|
|
+
|
|
|
|
|
cdeskjet.dev: $(cdeskjet_) page.dev
|
|
|
|
|
$(SETPDEV) cdeskjet $(cdeskjet_)
|
|
|
|
|
+
|
- Update the additional hp850 driver to newest release 1.3
- Since the author decided to put a version number into his archive,
we can now safely fetch the file from his site.
- patch-ad is useless now
- updated the configure and configure.batch script, to show all possible
drivers
- install hp850 drivers license and readme file in the gs doc dir
- update the DESCR file, mention the two add on packages in this port
- The new driver supports the following additional printers:
Support for HP DeskJet 670, 690, 850, 855, 870, 890, 1100 and 1600,
See announcement on http://bonk.ethz.ch/hp850/hp850.html
Please note, that some of the drivers have certain restrictions
and produce huge output files ... Please read the release notes !!!
The author makes suggestions on his website, what driver to choose
if you need a fast printout, see
http://bonk.ethz.ch/hp850/hp850-readme.1.3.html
1998-06-04 20:11:39 +00:00
|
|
|
+cdj670.dev: $(cdeskjet8_) page.dev
|
|
|
|
|
+ $(SETPDEV) cdj670 $(cdeskjet8_)
|
|
|
|
|
+
|
Major cleanup for ghostscript5 port.
- merged patch-af into patch-aa, both patches hacked unix-gcc.mak
- merged the scripts/{configure,configure.batch} changes into
patch-aa, so that unix-gcc.mak is hacked only by patch-aa
- when doing interactive configuration, every device driver is
now turned on, so you have to deselect devices
- when using BATCH compilation, you now get every supported device,
this one is especially for Satoshi, when making gs packages !
- Added a note into unix-gcc.mak, that DEVICE_DEVS now completely
are removed in the makefile, instead of this, the two configure
scripts now completely control, which devices have to be compiled in.
So, the configure target "patches" the unix-gcc.mak Makefile and
puts a DEVICE_DEVS line at line 1. When doing batch compilation
every device is included in this line, or the wanted devices ...
- The compilation option -DA4 is now included if you compile the port
by saying "make A4=yes".
I hope, I didn't forget a driver, look at that long line ;-)
BTW, I didn't create that DEVICE_DEVS line by hand, I did the
interactive installation, which created it automatically, and
after that I "stealed" that DEVICE_DEVS line for inclusion
into configure.batch ;-) So the devices in configure and configure.batch
are exactly the same, you only have to compare devices.mak with one
of the configure scripts.
BTW, should we nuke ghostscript4 ??? Does somebody know if any
port needs gs4 ???
1997-06-14 09:36:31 +00:00
|
|
|
+cdj850.dev: $(cdeskjet8_) page.dev
|
|
|
|
|
+ $(SETPDEV) cdj850 $(cdeskjet8_)
|
- Update the additional hp850 driver to newest release 1.3
- Since the author decided to put a version number into his archive,
we can now safely fetch the file from his site.
- patch-ad is useless now
- updated the configure and configure.batch script, to show all possible
drivers
- install hp850 drivers license and readme file in the gs doc dir
- update the DESCR file, mention the two add on packages in this port
- The new driver supports the following additional printers:
Support for HP DeskJet 670, 690, 850, 855, 870, 890, 1100 and 1600,
See announcement on http://bonk.ethz.ch/hp850/hp850.html
Please note, that some of the drivers have certain restrictions
and produce huge output files ... Please read the release notes !!!
The author makes suggestions on his website, what driver to choose
if you need a fast printout, see
http://bonk.ethz.ch/hp850/hp850-readme.1.3.html
1998-06-04 20:11:39 +00:00
|
|
|
+
|
|
|
|
|
+cdj890.dev: $(cdeskjet8_) page.dev
|
|
|
|
|
+ $(SETPDEV) cdj890 $(cdeskjet8_)
|
|
|
|
|
+
|
|
|
|
|
+cdj1600.dev: $(cdeskjet8_) page.dev
|
|
|
|
|
+ $(SETPDEV) cdj1600 $(cdeskjet8_)
|
Major cleanup for ghostscript5 port.
- merged patch-af into patch-aa, both patches hacked unix-gcc.mak
- merged the scripts/{configure,configure.batch} changes into
patch-aa, so that unix-gcc.mak is hacked only by patch-aa
- when doing interactive configuration, every device driver is
now turned on, so you have to deselect devices
- when using BATCH compilation, you now get every supported device,
this one is especially for Satoshi, when making gs packages !
- Added a note into unix-gcc.mak, that DEVICE_DEVS now completely
are removed in the makefile, instead of this, the two configure
scripts now completely control, which devices have to be compiled in.
So, the configure target "patches" the unix-gcc.mak Makefile and
puts a DEVICE_DEVS line at line 1. When doing batch compilation
every device is included in this line, or the wanted devices ...
- The compilation option -DA4 is now included if you compile the port
by saying "make A4=yes".
I hope, I didn't forget a driver, look at that long line ;-)
BTW, I didn't create that DEVICE_DEVS line by hand, I did the
interactive installation, which created it automatically, and
after that I "stealed" that DEVICE_DEVS line for inclusion
into configure.batch ;-) So the devices in configure and configure.batch
are exactly the same, you only have to compare devices.mak with one
of the configure scripts.
BTW, should we nuke ghostscript4 ??? Does somebody know if any
port needs gs4 ???
1997-06-14 09:36:31 +00:00
|
|
|
|
|
|
|
|
cdjcolor.dev: $(cdeskjet_) page.dev
|
|
|
|
|
$(SETPDEV) cdjcolor $(cdeskjet_)
|