AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2000.01.30 01:02 "libtiff in a M$ Windows Visual C++ 5.0 DLL for Borland Delphi 3,4,5", by Joris Van Damme
2000.01.31 14:46 "Re: libtiff in a M$ Windows Visual C++ 5.0 DLL for Borland Delphi 3,4,5", by Bruce Cameron
2000.01.31 15:05 "Re: libtiff in a M$ Windows Visual C++ 5.0 DLL for Borland Delphi 3,4,5", by Scott Wagner
2000.01.31 15:02 "Re: libtiff in a M$ Windows Visual C++ 5.0 DLL for Borland Delphi 3,4,5", by Frank Warmerdam
2000.01.31 18:29 "Re: Threadsafe MSVC implementation of LibTiff", by Scott Wagner
2000.02.05 01:06 "Re: threadsafety of libtiff 3.5.4?", by Frank Warmerdam

2000.01.31 15:05 "Re: libtiff in a M$ Windows Visual C++ 5.0 DLL for Borland Delphi 3,4,5", by Scott Wagner

Hi all,

From Frank Warmerdam:

>I have prepared zip files of libtiff.lib, libtiff.dll and the various tool >programs for Windows. This is intended to save folks the step of compiling >on windows when they don't need to modify the configuration options.

>
>They can be found at:
>
> ftp://ftp.remotesensing.org/pub/libtiff/libtiff_bin_354.zip
> ftp://ftp.remotesensing.org/pub/libtiff/tifftools_bin_354.zip

LibTiff (including its Windows DLL incarnation) is almost(!) reentrant. That is, the only pieces which are non-reentrant are the pieces which set up the warning and error handlers. For most uses, this is OK - set up your warning and error handlers at initialization; then you can handle multiple images with multiple TIFF handles without collisions.

/*********************************************************************
* Scott Wagner  (swagner@itek.com)    NOTICE: My personal information,
* Staff Engineer                      including my E-mail address, may
* Itek Graphix                        not be sold, distributed, or made
* Rochester, NY USA                   public without my consent.
*********************************************************************/