Building the TIFF Software Distribution

Linux 4gvps.4gvps.com 3.10.0-1127.18.2.vz7.163.46 #1 SMP Fri Nov 20 21:47:55 MSK 2020 x86_64
SOFT : Apache PHP : 7.4.33
/usr/share/doc/libtiff-devel-4.0.3/html/

38.135.39.45

[ NAME ]	[ SIZE ]	[ PERM ]	[ DATE ]	[ ACT ]
+FILE +DIR
images	dir	drwxr-xr-x	2024-11-02 01:15	R D
man	dir	drwxr-xr-x	2024-11-02 01:15	R D
TIFFTechNote2.html	34.861 KB	-rw-r--r--	2002-01-16 17:29	R E G D
addingtags.html	11.529 KB	-rw-r--r--	2004-09-10 14:43	R E G D
bugs.html	2.584 KB	-rw-r--r--	2008-09-03 14:57	R E G D
build.html	23.096 KB	-rw-r--r--	2012-02-18 21:36	R E G D
contrib.html	3.651 KB	-rw-r--r--	2006-01-03 01:42	R E G D
document.html	1.566 KB	-rw-r--r--	2006-08-01 17:24	R E G D
images.html	1.063 KB	-rw-r--r--	2006-01-02 23:50	R E G D
index.html	4.942 KB	-rw-r--r--	2012-09-22 15:56	R E G D
internals.html	18.785 KB	-rw-r--r--	2004-09-11 02:14	R E G D
intro.html	2.338 KB	-rw-r--r--	1999-08-09 20:21	R E G D
libtiff.html	36.556 KB	-rw-r--r--	2005-12-28 23:01	R E G D
misc.html	3.74 KB	-rw-r--r--	2007-03-08 03:42	R E G D
support.html	17.279 KB	-rw-r--r--	2005-12-28 23:01	R E G D
tools.html	6.595 KB	-rw-r--r--	2009-10-28 22:13	R E G D
v3.4beta007.html	3.804 KB	-rw-r--r--	1999-08-09 20:21	R E G D
v3.4beta016.html	3.929 KB	-rw-r--r--	1999-08-09 20:21	R E G D
v3.4beta018.html	2.585 KB	-rw-r--r--	1999-08-09 20:21	R E G D
v3.4beta024.html	5.213 KB	-rw-r--r--	1999-08-09 20:21	R E G D
v3.4beta028.html	5.842 KB	-rw-r--r--	1999-08-09 20:21	R E G D
v3.4beta029.html	2.704 KB	-rw-r--r--	1999-08-09 20:21	R E G D
v3.4beta031.html	3.247 KB	-rw-r--r--	1999-08-09 20:21	R E G D
v3.4beta032.html	2.631 KB	-rw-r--r--	1999-08-09 20:21	R E G D
v3.4beta033.html	2.234 KB	-rw-r--r--	1999-08-09 20:21	R E G D
v3.4beta034.html	2.11 KB	-rw-r--r--	1999-08-09 20:21	R E G D
v3.4beta035.html	1.75 KB	-rw-r--r--	1999-08-09 20:21	R E G D
v3.4beta036.html	4.46 KB	-rw-r--r--	1999-08-09 20:21	R E G D
v3.5.1.html	2.12 KB	-rw-r--r--	2006-01-03 01:42	R E G D
v3.5.2.html	3.196 KB	-rw-r--r--	2004-11-30 23:19	R E G D
v3.5.3.html	4.159 KB	-rw-r--r--	2004-11-30 23:19	R E G D
v3.5.4.html	2.32 KB	-rw-r--r--	2006-01-03 01:45	R E G D
v3.5.5.html	4.882 KB	-rw-r--r--	2004-11-30 23:19	R E G D
v3.5.6-beta.html	5.963 KB	-rw-r--r--	2006-03-19 03:26	R E G D
v3.5.7.html	9.793 KB	-rw-r--r--	2004-11-30 23:19	R E G D
v3.6.0.html	16.392 KB	-rw-r--r--	2003-10-04 11:38	R E G D
v3.6.1.html	6.665 KB	-rw-r--r--	2003-12-24 22:14	R E G D
v3.7.0.html	4.063 KB	-rw-r--r--	2005-01-05 02:51	R E G D
v3.7.0alpha.html	8.887 KB	-rw-r--r--	2006-03-19 03:26	R E G D
v3.7.0beta.html	4.846 KB	-rw-r--r--	2006-03-19 03:26	R E G D
v3.7.0beta2.html	3.536 KB	-rw-r--r--	2006-03-19 03:26	R E G D
v3.7.1.html	8.005 KB	-rw-r--r--	2004-12-20 19:31	R E G D
v3.7.2.html	7.838 KB	-rw-r--r--	2005-03-16 15:27	R E G D
v3.7.3.html	8.062 KB	-rw-r--r--	2006-01-08 18:56	R E G D
v3.7.4.html	4.165 KB	-rw-r--r--	2005-12-02 23:01	R E G D
v3.8.0.html	6.672 KB	-rw-r--r--	2006-01-08 18:56	R E G D
v3.8.1.html	7.87 KB	-rw-r--r--	2006-03-13 14:52	R E G D
v3.8.2.html	4.189 KB	-rw-r--r--	2006-03-23 14:54	R E G D
v3.9.0beta.html	11.446 KB	-rw-r--r--	2009-08-20 22:57	R E G D
v3.9.1.html	3.12 KB	-rw-r--r--	2009-08-28 18:54	R E G D
v3.9.2.html	3.318 KB	-rw-r--r--	2009-11-04 17:38	R E G D
v4.0.0.html	10.506 KB	-rw-r--r--	2011-04-09 21:01	R E G D
v4.0.1.html	2.973 KB	-rw-r--r--	2012-02-18 21:53	R E G D
v4.0.2.html	2.947 KB	-rw-r--r--	2012-09-22 15:40	R E G D
REQUEST EXIT

Building the Software Distribution

Building on a UNIX System

In general, the software is designed such that the following should be ``make-able'' in each directory:

Build Trees

Otherwise, you can configure a build tree that is parallel to the source tree hierarchy (or in some completely different place) but which contains only configured files and files created during the build procedure.

Configuration Options

A second function of the configure script is to set the default configuration parameters for the software. Of particular note are the directories where the software is to be installed. By default the software is installed in the /usr/local hierarchy. To change this behaviour the appropriate parameters can be specified on the command line to configure. Run ./configure --help to get a full list of possible options. Standard installation related options are shown below.

Configuring Optional Packages/Support

Building the Software under Windows 95/98/NT/2000 with MS VC++

The source package is delivered using Unix line termination conventions, which work with MSVC but do not work with Windows 'notepad'. If you use unzip from the Info-Zip package, you can extract the files using Windows normal line termination conventions with a command similar to:

By default libtiff expects that a pre-built zlib and jpeg library are provided by the user. If this is not the case, then you may edit libtiff\tiffconf.h using a text editor (e.g. notepad) and comment out the entries for JPEG_SUPPORT, PIXARLOG_SUPPORT, and ZIP_SUPPORT. Ignore the comment at the top of the file which says that it has no influence on the build, because the statement is not true for Windows. However, by taking this approach, libtiff will not be able to open some TIFF files.

This will build the library file libtiff\libtiff\libtiff.lib. This can be used in Win32 programs. You may want to adjust the build options before start compiling. All parameters contained in the nmake.opt file.This is a plain text file you can open with your favorite text editor.

The makefile also builds a DLL (libtiff.dll) with an associated import library (libtiff_i.lib). Any builds using libtiff will need to include the LIBTIFF\LIBTIFF directory in the include path.

The libtiff\tools\makefile.vc should build .exe's for all the standard TIFF tool programs.

Building the Software on a VMS System

This release has been tested on OpenVMS/VAX 5.5-2, using VAX C 3.2. A previous release was tested under OpenVMS/AXP ?.? using DEC C ?.?, it is believed that this release as well works on AXP. The code contains some GNU C specific things. This does *not* imply, however, that the VAX/GCC configuration has been tested, *it has not*.

The command procedures (MAKEVMS.COM) for building the library and tools, is believed to choose the correct options for the VAX and AXP cases automatically.

On the AXP, IEEE floating point is used by default. If you want VAX floating point, remove the /FLOAT=IEEE_FLOAT qualifier, and change HAVE_IEEEFP=1 to HAVE_IEEEFP=0 in the MAKEVMS.COM files in both the libtiff and tools directories.

Compiling your own program on a VMS system:

Linking your own program to the TIFF library on a VMS system:

Method 2 gives somewhat longer link time and larger .EXE files, but does not require TIFFSHR to be defined. This method is recommended if you want to run your program on another machine, and for some reason don't want to have the library on that machine. If you plan to have more than one program (including the tools) on the machine, it is recommended that you copy the library to the other machine and use method 1.

Building the Software on Other Systems

The library requires two files that are generated on-the-fly. The file tif_fax3sm.c has the state tables for the Group 3 and Group 4 decoders. This file is generated by the mkg3states program on a UNIX system; for example,

The second file required to build the library, version.h, contains the version information returned by the TIFFGetVersion routine. This file is built on most systems using the mkversion program and the contents of the VERSION and tiff.alpha files; for example,

Otherwise, when building the library on a non-UNIX system be sure to consult the files tiffcomp.h and tiffconf.h. The former contains system compatibility definitions while the latter is provided so that the software configuration can be controlled on systems that do not support the make facility for building the software.

Systems without a 32-bit compiler may not be able to handle some of the codecs in the library; especially the Group 3 and 4 decoder. If you encounter problems try disabling support for a particular codec; consult the documentation.

Programs in the tools directory are written to assume an ANSI C compilation environment. There may be a few POSIX'isms as well. The code in the port directory is provided to emulate routines that may be missing on some systems. On UNIX systems the configure script automatically figures out which routines are not present on a system and enables the use of the equivalent emulation routines from the port directory. It may be necessary to manually do this work on a non-UNIX system.

Checking out the Software

Assuming you have working versions of tiffgt and tiffsv, you can just use them to view any of the sample images available for testing (see the section on obtaining the test images). Otherwise, you can do a cursory check of the library with the tiffcp and tiffcmp programs. For example,