AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

1994.02.11 16:31 "LIBTIFFW followup.", by Soren Pingel Dalsgaard
1994.02.11 03:23 "Re: LIBTIFFW followup.", by Richard Minner

1994.02.11 16:31 "LIBTIFFW followup.", by Soren Pingel Dalsgaard

I have received an amazing amount of mail requesting the library.

1) Where should I put the sources. I could try to ftp-upload it to wuarchive.wustl.edu, but it is busy most of the time. I am checking if it is possible to make it available from our server here in Denmark.

2a) How is it compiled? The library will compile if you use Microsoft Visual C/C++. Whether or not Borland C/C++ version 3.1 or 4.0 will do I don't know. We have just bought Borland C/C++ 4.0, and I think that I will be able to confirm that it works within long. There is next to no Windows specific code in the revised library.

2b) It is currently compiled as a LIBTIFFW.LIB file suitable for linking into a windows DLL. The reason for this is that we needed a TIFF.DLL that supports selection of compression method and related flags. In order to compile LIBTIFFW as a separate DLL requeres changing the compile parameters and creation of a .DEF file. If someone comes up with this, I'll be glad to know about it for inclusion in the next revision.

3) It has been pointed out that libtiff is a LIBRARY and therefore the error and warning functions should not need chaging. My opinion is that the error and warning routines should provide a sensible default action in the present environment. fprintf(stderr, ...) is NOT a sensible default action inside windows and have thus been changed.

4) I have mainly focused on TIFF writing during our tests.

1 revisited) I have made arrangements with our system administrator that the library can be obtained from our site using anonymous ftp. It is available at daimi.aau.dk:pub/pc/v33b_win.arj.

You should get sgi.com:graphics/tiff/v3.3beta002.src.tar.Z. This file contains complete documentation.

Yes it is my hope that (some of) these changes will eventually be included in the original libtiff library.

***IMPORTANT***

The way I have implemented byte ordering is: The first letter of the mode string supplied to TIFFOpen is 'r' for read, 'w' for write or 'a' for append. If opening for writing, the second letter is 'l' to force little endian or 'b' to force big-endian. This was done because the tiff header is written during open which is the first operation applied to a tiff file.

I have probably forgotten to mention something very important, so another follow-up will most likely be posted soon.

New versions will be put under the same filename. This is because our administrator doesn't want our site to be filled with software packages that our university doesn't support. This port of libtiff has nothing to do with the university. My former boss paid me to do the changes and to get a copy of what I eventually would come up with.

/Soren

---

Soren Pingel Dalsgaard
pingel@daimi.aau.dk
Department of Computer Science
Aarhus University
Ny Munkegade 116
DK-8000 Aarhus C
DENMARK