• Home
  • History
  • Annotate
  • only in this directory
NameDateSize

..01-Mar-201322

conf.batH A D13-Aug-2004340

Makefile.libH A D13-Aug-20047.4 KiB

Makefile.toolsH A D13-Aug-20045.8 KiB

Makefile.topH A D13-Aug-20042.1 KiB

port.hH A D13-Aug-2004572

READMEH A D13-Aug-20041.7 KiB

README

1
2This directory contains the files necessary to build the free TIFF library
3with the DJGPP v2 compiler under MSDOS. Since DJGPP defines the unix flag,
4I have created a port.h instead of putting the necessary defines into
5tiffcomp.h. Makefiles are included for the top level and the libtiff and
6tools directories.
7
8All you have to do is copy the files into the respective directories and run
9make. If you want, you can use the conf.bat to do that for you, make sure that
10the file is stored with MSDOS text EOL-convention (CR/LF), otherwise the
11command.com will not do anything (if you used unzip, use the -a option,
12otherwise edit the file and save it again).
13
14Note that you probably will not be able to built the library with the v1.x
15versions of djgpp, due to two problems. First, the top makefile calls a
16sub-make for each directory and you are likely to run out of memory, since
17each recursive invocation of a djgpp v1.x program requires about 130k, to
18avoid that, you can enter the directories manually and call make (well, there
19are only two dirs). The 2nd problem is that djgpp 1.x doesn't call the
20coff2exe (stubify) program when creating an executable. This means that all
21programs compiled are not converted to exe and consequently are not available
22for calling directly. For the tools directory, you can just call coff2exe for
23each program after make finishes, but in the libtiff directory, a few programs
24are created during the make process that have to be called for make to
25continue (e.g. mkg3states). Make will probably report an error at each
26such stage. To fix that, either add a coff2exe call before each program is
27called or call coff2exe manually and rerun make (there 2-3 such programs).
28
29Alexander Lehmann <alex@hal.rhein-main.de>
30
31