1<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2<html> 3<head> 4<meta name="generator" content= 5"HTML Tidy for Linux (vers 25 March 2009), see www.w3.org"> 6<title>Building the TIFF Software Distribution</title> 7</head> 8<body bgcolor="white"> 9<h1><font face="Arial, Helvetica, Sans"><img src= 10"images/cramps.gif" width="159" height="203" align="left" border= 11"1" hspace="6"> Building the Software Distribution</font></h1> 12<ul> 13<li><a href="#UNIX">Building on a UNIX system</a>.</li> 14<li><a href="#PC">Building on an MS-DOS or Windows system</a>.</li> 15<li><a href="#VMS">Building on a VMS system</a>.</li> 16<li><a href="#Other">Building the Software on Other 17Systems</a></li> 18</ul> 19<br clear="left"> 20This chapter contains step-by-step instructions on how to configure 21and build the TIFF software distribution. The software is most 22easily built on a UNIX system, but with a little bit of work it can 23easily be built and used on other non-UNIX platforms. 24<hr> 25<a name="UNIX" id="UNIX"></a> 26<h2>Building on a UNIX System</h2> 27To build the software on a UNIX system you need to first run the 28configure shell script that is located in the top level of the 29source directory. This script probes the target system for 30necessary tools and functions and constructs a build environment in 31which the software may be compiled. Once configuration is done, you 32simply run <tt>make</tt> (or <tt>gmake</tt>) to build the software 33and then <tt>make install</tt> to do the installation; for example: 34<div style="margin-left: 2em"> 35<pre> 36hyla% <b>cd ./tiff-4.0.0</b> 37hyla% <b>./configure</b> 38 <i>...lots of messages...</i> 39hyla% <b>make</b> 40 <i>...lots of messages...</i> 41hyla% <b>make check</b> 42 <i>...lots of messages...</i> 43hyla# <b>make install</b> 44</pre></div> 45Supplied makefiles are dependent on a <tt>make</tt> utility and a C 46(and optionally a C++ compiler), so you will need these tools. 47<p>In general, the software is designed such that the following 48should be ``<i>make-able</i>'' in each directory:</p> 49<div style="margin-left: 2em"> 50<pre> 51make [all] build stuff 52make check run the test suite 53make install build&install stuff 54make clean remove .o files, executables and cruft 55make distclean remove everything, that can be recreated 56</pre></div> 57Note that after running "<tt>make distclean</tt>" the 58<tt>configure</tt> script must be run again to create the Makefiles 59and other make-related files. <a name="BuildTrees" id= 60"BuildTrees"></a> 61<hr width="65%" align="right"> 62<h3>Build Trees</h3> 63There are two schemes for configuring and building the software. If 64you intend to build the software for only one target system, you 65can configure the software so that it is built in the same 66directories as the source code. 67<div style="margin-left: 2em"> 68<pre> 69hyla% <b>gzip -dc tiff-4.0.0.tar.gz | tar -xf -</b> 70hyla% <b>cd ./tiff-4.0.0</b> 71hyla% <b>./configure</b> 72hyla% <b>make</b> 73hyla% <b>make check</b> 74hyla% <b>make install</b> 75</pre></div> 76<p>Otherwise, you can configure a build tree that is parallel to 77the source tree hierarchy (or in some completely different place) 78but which contains only configured files and files created during 79the build procedure.</p> 80<div style="margin-left: 2em"> 81<pre> 82hyla% <b>gzip -dc tiff-4.0.0.tar.gz | tar -xf -</b> 83hyla% <b>mkdir tiff-4.0.0-build</b> 84hyla% <b>cd ./tiff-4.0.0-build</b> 85hyla% <b>../tiff-4.0.0/configure</b> 86hyla% <b>make</b> 87hyla% <b>make check</b> 88hyla% <b>make install</b> 89</pre></div> 90This second scheme is useful for: 91<ul> 92<li>building multiple targets from a single source tree</li> 93<li>building from a read-only source tree (e.g. if you receive the 94distribution on CD-ROM)</li> 95<li>sharing the source files via a network, but building on 96multiple systems</li> 97</ul> 98<a name="ConfigOptions" id="ConfigOptions"></a> 99<hr width="65%" align="right"> 100<h3>Configuration Options</h3> 101The configuration process is critical to the proper compilation, 102installation, and operation of the software. The configure script 103runs a series of tests to decide whether or not the target system 104supports required functionality and, if it does not, whether it can 105emulate or workaround the missing functions. This procedure is 106fairly complicated and, due to the nonstandard nature of most UNIX 107systems, prone to error. The first time that you configure the 108software for use you should check the output from the configure 109script and look for anything that does not make sense for your 110system. 111<p>A second function of the configure script is to set the default 112configuration parameters for the software. Of particular note are 113the directories where the software is to be installed. By default 114the software is installed in the <b>/usr/local</b> hierarchy. To 115change this behaviour the appropriate parameters can be specified 116on the command line to configure. Run <b>./configure --help</b> to 117get a full list of possible options. Standard installation related 118options are shown below.</p> 119<pre> 120<tt> 121Installation directories: 122 --prefix=PREFIX install architecture-independent files in PREFIX 123 [/usr/local] 124 --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX 125 [PREFIX] 126 127By default, `make install' will install all the files in 128`/usr/local/bin', `/usr/local/lib' etc. You can specify 129an installation prefix other than `/usr/local' using `--prefix', 130for instance `--prefix=$HOME'. 131 132For better control, use the options below. 133 134Fine tuning of the installation directories: 135 --bindir=DIR user executables [EPREFIX/bin] 136 --sbindir=DIR system admin executables [EPREFIX/sbin] 137 --libexecdir=DIR program executables [EPREFIX/libexec] 138 --sysconfdir=DIR read-only single-machine data [PREFIX/etc] 139 --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] 140 --localstatedir=DIR modifiable single-machine data [PREFIX/var] 141 --libdir=DIR object code libraries [EPREFIX/lib] 142 --includedir=DIR C header files [PREFIX/include] 143 --oldincludedir=DIR C header files for non-gcc [/usr/include] 144 --datarootdir=DIR read-only arch.-independent data root [PREFIX/share] 145 --datadir=DIR read-only architecture-independent data [DATAROOTDIR] 146 --localedir=DIR locale-dependent data [DATAROOTDIR/locale] 147 --mandir=DIR man documentation [DATAROOTDIR/man] 148 --docdir=DIR documentation root [DATAROOTDIR/doc/tiff] 149 --htmldir=DIR html documentation [DOCDIR] 150 151Program names: 152 --program-prefix=PREFIX prepend PREFIX to installed program names 153 --program-suffix=SUFFIX append SUFFIX to installed program names 154 --program-transform-name=PROGRAM run sed PROGRAM on installed program names 155</tt> 156</pre> 157<a name="Packages" id="Packages"></a> 158<hr width="65%" align="right"> 159<h3>Configuring Optional Packages/Support</h3> 160The TIFF software comes with several packages that are installed 161only as needed, or only if specifically configured at the time the 162configure script is run. Packages can be configured via the 163<b>configure</b> script commandline parameters. 164<dl> 165<dt><i>Static/Shared Objects Support</i></dt> 166<dd><tt>--enable-shared[=PKGS] build shared 167libraries [default=yes]<br> 168--enable-static[=PKGS] build static 169libraries [default=yes]</tt> 170<p>These options control whether or not to configure the software 171to build a shared and static binaries for the TIFF library. Use of 172shared libraries can significantly reduce the disk space needed for 173users of the TIFF software. If shared libarries are not used then 174the code is statically linked into each application that uses it. 175By default both types of binaries is configured.</p> 176<p> 177<tt>--enable-rpath Enable 178runtime linker paths (-R libtool option)</tt></p> 179<p>Add library directories (see other options below) to the TIFF 180library run-time linker path.</p> 181<p><tt>--enable-ld-version-script Enable linker version 182script (default is disabled)</tt></p> 183<p>Add shared library symbol versioning on ELF-based systems (e.g. 184Linux and FreeBSD) which use the GNU linker. This is needed if 185several major versions of libtiff might be loaded at once into the 186same program.</p> 187</dd> 188<dt><i>JPEG Support</i></dt> 189<dd><tt>--disable-jpeg disable IJG JPEG 190library usage (required for JPEG compression, enabled by default) 191--with-jpeg-include-dir=DIR location of IJG 192JPEG library headers 193--with-jpeg-lib-dir=DIR location of IJG JPEG 194library binary)</tt></dd> 195<dd>The <tt>JPEG</tt> package enables support for the handling of 196TIFF images with JPEG-encoded data. Support for JPEG-encoded data 197requires the Independent JPEG Group (IJG) <tt>libjpeg</tt> 198distribution; this software is available at <a href= 199"http://www.ijg.org/">http://www.ijg.org/</a>. <b>configure</b> 200script automatically tries to search for a working IJG JPEG 201installation. If it fails to find library, JPEG support will be 202automatically disabled.If you want specify the exact paths to 203library binary and headers, use above switches for that.</dd> 204<dt><i>ZIP Support</i></dt> 205<dd>The <tt>ZIP</tt> support enables support for the handling of 206TIFF images with deflate-encoded data. Support for deflate-encoded 207data requires the freely available <tt>zlib</tt> distribution 208written by Jean-loup Gailly and Mark Adler; this software is 209available at <a href= 210"http://www.zlib.org/">http://www.zlib.org/</a>. If ZIP support is 211enabled the <tt>DIRS_LIBINC</tt> and <tt>DIR_GZLIB</tt> parameters 212should also be set (see below). By default this package is not 213configured.</dd> 214</dl> 215<a name="Sample" id="Sample"></a> 216<hr width="65%" align="right"> 217<a name="PC" id="PC"></a> 218<h2>Building the Software under Windows 2000/XP/7/8/10 with MS 219VC++</h2> 220With Microsoft Visual C++ installed, and properly configured for 221commandline use (you will likely need to source VCVARS32.BAT in 222AUTOEXEC.bAT or somewhere similar) you should be able to use the 223provided <tt>makefile.vc</tt>. 224<p>The source package is delivered using Unix line termination 225conventions, which work with MSVC but do not work with Windows 226'notepad'. If you use unzip from the <a href= 227"http://www.info-zip.org/pub/infozip/">Info-Zip</a> package, you 228can extract the files using Windows normal line termination 229conventions with a command similar to:</p> 230<pre> 231 unzip -aa -a tiff-4.0.0.zip 232</pre> 233<p>By default the nmake-based libtiff build does not depend on any 234additional libraries. Normally libtiff should be built with at least 235JPEG and ZIP support so that it can open JPEG and ZIP-compressed TIFF 236files. In order to add additional libraries (e.g. libjpeg, zlib, 237jbigkit), build those libraries according to their own particular 238build instructions, and then edit 'nmake.opt' (using a capable 239plain-text editor) to enable use of the libraries, including 240specifying where the libraries are installed. It is also necessary to 241edit libtiff/tiffconf.vc.h to enable the related configuration defines 242(<em>JPEG_SUPPORT</em>, <em>OJPEG_SUPPORT</em>, <em>PIXARLOG_SUPPORT</em>, 243<em>ZIP_SUPPORT</em>), or to disable features which are normally 244included by default. Ignore the comment at the top of the 245libtiff/tiffconf.vc.h file which says that it has no influence on the 246build, because the statement is not true for Windows. Please note that 247the nmake build copies tiffconf.vc.h to tiffconf.h, and copies 248tif_config.vc.h to tif_config.h, overwriting any files which may be 249present. Likewise, the 'nmake clean' step removes those files.</p> 250<p>To build using the provided makefile.vc you may use:</p> 251<pre> 252 C:\tiff-4.0.0> nmake /f makefile.vc clean 253 C:\tiff-4.0.0> nmake /f makefile.vc 254 255 or (the hard way) 256 257 C:\tiff-4.0.0> cd port 258 C:\tiff-4.0.0\port> nmake /f makefile.vc clean 259 C:\tiff-4.0.0\port> nmake /f makefile.vc 260 C:\tiff-4.0.0> cd ../libtiff 261 C:\tiff-4.0.0\libtiff> nmake /f makefile.vc clean 262 C:\tiff-4.0.0\libtiff> nmake /f makefile.vc 263 C:\tiff-4.0.0\libtiff> cd ..\tools 264 C:\tiff-4.0.0\tools> nmake /f makefile.vc clean 265 C:\tiff-4.0.0\tools> nmake /f makefile.vc 266</pre> 267<p>This will build the library 268file <tt>libtiff\libtiff\libtiff.lib</tt>.</p> 269<p>The makefile also builds a DLL (libtiff.dll) with an associated 270import library (libtiff_i.lib). Any builds using libtiff will need to 271include the LIBTIFF\LIBTIFF directory in the include path.</p> 272<p>The <tt>libtiff\tools\makefile.vc</tt> should build .exe's for 273all the standard TIFF tool programs.</p> 274<hr> 275<a name="VMS" id="VMS"></a> 276<h2>Building the Software on a VMS System</h2> 277The VMS port was done by Karsten Spang (<a href= 278"mailto:[email protected]">[email protected]</a>), who also "sort of" 279maintains it. The VMS specific files are not in the main 280directories. Instead they are placed under 281<tt>[.CONTRIB.VMS...]</tt> in the distribution tree. Installation: 282It is assumed that you have unpacked the tar file into a VMS 283directory tree, in this text called DISK:[TIFF]. 284<ol> 285<li>Move the VMS specific files to their proper directories. 286<pre> 287$ SET DEFAULT DISK:[TIFF.CONTRIB.VMS] 288$ RENAME [.LIBTIFF]*.* [-.-.LIBTIFF] 289$ RENAME [.TOOLS]*.* [-.-.TOOLS] 290</pre></li> 291<li>Compile the library. 292<pre> 293$ SET DEFAULT DISK:[TIFF.LIBTIFF] 294$ @MAKEVMS 295</pre></li> 296<li>Compile the tools. 297<pre> 298$ SET DEFAULT DISK:[TIFF.TOOLS] 299$ @MAKEVMS 300</pre></li> 301<li>Define the programs. 302<pre> 303$ DEFINE TIFFSHR DISK:[TIFF.LIBTIFF]TIFFSHR 304$ FAX2PS :==$DISK:[TIFF.TOOLS]FAX2PS 305$ FAX2TIFF :==$DISK:[TIFF.TOOLS]FAX2TIFF 306$ GIF2TIFF :==$DISK:[TIFF.TOOLS]GIF2TIFF 307$ PAL2RGB :==$DISK:[TIFF.TOOLS]PAL2RGB 308$ PPM2TIFF :==$DISK:[TIFF.TOOLS]PPM2TIFF 309$ RAS2TIFF :==$DISK:[TIFF.TOOLS]RAS2TIFF 310$ RGB2YCBCR :==$DISK:[TIFF.TOOLS]RGB2YCBCR 311$ THUMBNAIL :==$DISK:[TIFF.TOOLS]THUMBNAIL 312$ TIFF2BW :==$DISK:[TIFF.TOOLS]TIFF2BW 313$ TIFF2PS :==$DISK:[TIFF.TOOLS]TIFF2PS 314$ TIFFCMP :==$DISK:[TIFF.TOOLS]TIFFCMP 315$ TIFFCP :==$DISK:[TIFF.TOOLS]TIFFCP 316$ TIFFDITHER:==$DISK:[TIFF.TOOLS]TIFFDITHER 317$ TIFFDUMP :==$DISK:[TIFF.TOOLS]TIFFDUMP 318$ TIFFINFO :==$DISK:[TIFF.TOOLS]TIFFINFO 319$ TIFFMEDIAN:==$DISK:[TIFF.TOOLS]TIFFMEDIAN 320$ TIFFSPLIT :==$DISK:[TIFF.TOOLS]TIFFSPLIT 321$ YCBCR :==$DISK:[TIFF.TOOLS]YCBCR 322</pre></li> 323</ol> 324You will want to add these lines to your <tt>LOGIN.COM</tt> file, 325after changing the name of the directory that you have used on your 326machine. 327<p>This release has been tested on OpenVMS/VAX 5.5-2, using VAX C 3283.2. A previous release was tested under OpenVMS/AXP ?.? using DEC 329C ?.?, it is believed that this release as well works on AXP. The 330code contains some GNU C specific things. This does *not* imply, 331however, that the VAX/GCC configuration has been tested, *it has 332not*.</p> 333<p>The command procedures (<tt>MAKEVMS.COM</tt>) for building the 334library and tools, is believed to choose the correct options for 335the VAX and AXP cases automatically.</p> 336<p>On the AXP, IEEE floating point is used by default. If you want 337VAX floating point, remove the <tt>/FLOAT=IEEE_FLOAT</tt> 338qualifier, and change <tt>HAVE_IEEEFP=1</tt> to 339<tt>HAVE_IEEEFP=0</tt> in the <tt>MAKEVMS.COM</tt> files in both 340the <b>libtiff</b> and <b>tools</b> directories.</p> 341<h3>Compiling your own program on a VMS system:</h3> 342When compiling a source file in which you <tt>"#include 343<tiffio.h>"</tt>, use the following command 344<pre> 345 $ CC/INCLUDE=DISK:[TIFF.LIBTIFF] 346</pre> 347This ensures that the header file is found. On the AXP, also add 348<tt>/FLOAT=IEEE_FLOAT</tt> (if used when building the library). 349<h3>Linking your own program to the TIFF library on a VMS 350system:</h3> 351You can link to the library in two ways: Either using the shareable 352library, or using the object library. On the VAX these 353possibilities are: 354<ol> 355<li>Using the shareable TIFF library. 356<pre> 357$ LINK MY_PROGRAM,DISK:[TIFF.LIBTIFF]TIFF/OPTIONS,SYS$INPUT:/OPTIONS 358 SYS$SHARE:VAXCRTL/SHAREABLE 359</pre></li> 360<li>Using the TIFF object library. 361<pre> 362$ LINK MY_PROGRAM, - 363 DISK:[TIFF.LIBTIFF]TIFF/LIBRARY/INCLUDE=(TIF_FAX3SM,TIF_CODEC), - 364 SYS$INPUT:/OPTIONS 365 SYS$SHARE:VAXCRTL/SHAREABLE 366</pre></li> 367</ol> 368On AXP (and possibly also using DEC C on VAX) the corresponding 369commands are 370<ol> 371<li>Using the shareable TIFF library. 372<pre> 373$ LINK MY_PROGRAM,DISK:[TIFF.LIBTIFF]TIFF/OPTIONS 374</pre></li> 375<li>Using the TIFF object library. 376<pre> 377$ LINK MY_PROGRAM,DISK:[TIFF.LIBTIFF]TIFF/LIBRARY 378</pre></li> 379</ol> 380Method 1 uses the shortest link time and smallest <tt>.EXE</tt> 381files, but it requires that <tt>TIFFSHR</tt> is defined as above at 382link time and <strong>at run time</strong>. Using the compilation 383procedure above, the tools are linked in this way. 384<p>Method 2 gives somewhat longer link time and larger 385<tt>.EXE</tt> files, but does not require <tt>TIFFSHR</tt> to be 386defined. This method is recommended if you want to run your program 387on another machine, and for some reason don't want to have the 388library on that machine. If you plan to have more than one program 389(including the tools) on the machine, it is recommended that you 390copy the library to the other machine and use method 1.</p> 391<hr> 392<a name="Other" id="Other"></a> 393<h2>Building the Software on Other Systems</h2> 394This section contains information that might be useful if you are 395working on a non-UNIX system that is not directly supported. All 396library-related files described below are located in the 397<b>libtiff</b> directory. 398<p>The library requires two files that are generated 399<i>on-the-fly</i>. The file <b>tif_fax3sm.c</b> has the state 400tables for the Group 3 and Group 4 decoders. This file is generated 401by the <tt>mkg3states</tt> program on a UNIX system; for 402example,</p> 403<div style="margin-left: 2em"> 404<pre> 405<tt> 406cd libtiff 407cc -o mkg3states mkg3states.c 408rm -f tif_fax3sm.c 409./mkg3states -c const tif_fax3sm.c 410</tt> 411</pre></div> 412The <tt>-c</tt> option can be used to control whether or not the 413resutling tables are generated with a <tt>const</tt> declaration. 414The <tt>-s</tt> option can be used to specify a C storage class for 415the table declarations. The <tt>-b</tt> option can be used to force 416data values to be explicitly bracketed with ``{}'' (apparently 417needed for some MS-Windows compilers); otherwise the structures are 418emitted in as compact a format as possible. Consult the source code 419for this program if you have questions. 420<p>The second file required to build the library, <b>version.h</b>, 421contains the version information returned by the 422<tt>TIFFGetVersion</tt> routine. This file is built on most systems 423using the <tt>mkversion</tt> program and the contents of the 424<tt>VERSION</tt> and <tt>tiff.alpha</tt> files; for example,</p> 425<div style="margin-left: 2em"> 426<pre> 427cd libtiff 428cc -o mkversion mkversion.c 429rm -f version.h 430./mkversion -v ../VERSION -a ../dist/tiff.alpha version.h 431</pre></div> 432<p>Otherwise, when building the library on a non-UNIX system be 433sure to consult the files <b>tiffcomp.h</b> and <b>tiffconf.h</b>. 434The former contains system compatibility definitions while the 435latter is provided so that the software configuration can be 436controlled on systems that do not support the make facility for 437building the software.</p> 438<p>Systems without a 32-bit compiler may not be able to handle some 439of the codecs in the library; especially the Group 3 and 4 decoder. 440If you encounter problems try disabling support for a particular 441codec; consult the <a href= 442"internals.html#Config">documentation</a>.</p> 443<p>Programs in the tools directory are written to assume an ANSI C 444compilation environment. There may be a few POSIX'isms as well. The 445code in the <b>port</b> directory is provided to emulate routines 446that may be missing on some systems. On UNIX systems the 447<tt>configure</tt> script automatically figures out which routines 448are not present on a system and enables the use of the equivalent 449emulation routines from the <b>port</b> directory. It may be 450necessary to manually do this work on a non-UNIX system. <a name= 451"Testing" id="Testing"></a></p> 452<hr> 453<h2>Checking out the Software</h2> 454<p>Assuming you have working versions of <tt>tiffgt</tt> and 455<tt>tiffsv</tt>, you can just use them to view any of the sample 456images available for testing (see the <a href="images.html">section 457on obtaining the test images</a>). Otherwise, you can do a cursory 458check of the library with the <tt>tiffcp</tt> and <tt>tiffcmp</tt> 459programs. For example,</p> 460<div style="margin-left: 2em"> 461<pre> 462tiffcp -lzw cramps.tif x.tif 463tiffcmp cramps.tif x.tif 464</pre></div> 465<p>(<tt>tiffcmp</tt> should be silent if the files compare 466correctly). <a name="TOC" id="TOC"></a></p> 467<hr> 468<h2>Table of Contents</h2> 469The following files makup the core library: 470<pre> 471libtiff/tiff.h TIFF spec definitions 472libtiff/tiffcomp.h non-UNIX OS-compatibility definitions 473libtiff/tiffconf.h non-UNIX configuration definitions 474libtiff/tiffio.h public TIFF library definitions 475libtiff/tiffiop.h private TIFF library definitions 476libtiff/t4.h CCITT Group 3/4 code tables+definitions 477libtiff/tif_dir.h private defs for TIFF directory handling 478libtiff/tif_fax3.h CCITT Group 3/4-related definitions 479libtiff/tif_predict.h private defs for Predictor tag support 480libtiff/uvcode.h LogL/LogLuv codec-specific definitions 481libtiff/version.h version string (generated by Makefile) 482libtiff/tif_apple.c Apple-related OS support 483libtiff/tif_atari.c Atari-related OS support 484libtiff/tif_aux.c auxilary directory-related functions 485libtiff/tif_close.c close an open TIFF file 486libtiff/tif_codec.c configuration table of builtin codecs 487libtiff/tif_compress.c compression scheme support 488libtiff/tif_dir.c directory tag interface code 489libtiff/tif_dirinfo.c directory known tag support code 490libtiff/tif_dirread.c directory reading code 491libtiff/tif_dirwrite.c directory writing code 492libtiff/tif_dumpmode.c "no" compression codec 493libtiff/tif_error.c library error handler 494libtiff/tif_fax3.c CCITT Group 3 and 4 codec 495libtiff/tif_fax3sm.c G3/G4 state tables (generated by mkg3states) 496libtiff/tif_flush.c i/o and directory state flushing 497libtiff/tif_getimage.c TIFFRGBAImage support 498libtiff/tif_jpeg.c JPEG codec (interface to the IJG distribution) 499libtiff/tif_luv.c SGI LogL/LogLuv codec 500libtiff/tif_lzw.c LZW codec 501libtiff/tif_msdos.c MSDOS-related OS support 502libtiff/tif_next.c NeXT 2-bit scheme codec (decoding only) 503libtiff/tif_open.c open and simply query code 504libtiff/tif_packbits.c Packbits codec 505libtiff/tif_pixarlog.c Pixar codec 506libtiff/tif_predict.c Predictor tag support 507libtiff/tif_print.c directory printing support 508libtiff/tif_read.c image data reading support 509libtiff/tif_strip.c some strip-related code 510libtiff/tif_swab.c byte and bit swapping support 511libtiff/tif_thunder.c Thunderscan codec (decoding only) 512libtiff/tif_tile.c some tile-related code 513libtiff/tif_unix.c UNIX-related OS support 514libtiff/tif_version.c library version support 515libtiff/tif_vms.c VMS-related OS support 516libtiff/tif_warning.c library warning handler 517libtiff/tif_win3.c Windows-3.1-related OS support 518libtiff/tif_win32.c Win32 (95/98/NT) related OS support 519libtiff/tif_write.c image data writing support 520libtiff/tif_zip.c Deflate codec 521 522libtiff/mkg3states.c program to generate G3/G4 decoder state tables 523libtiff/mkspans.c program to generate black-white span tables 524libtiff/mkversion.c program to generate libtiff/version.h. 525</pre> 526<hr> 527Last updated: $Date: 2015-06-21 18:21:28 $ 528</body> 529</html> 530
