AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2007.06.29 11:04 "[Tiff] Suggested Source Changes for Building libtiff Under Windows", by Kevin Myers
2007.06.29 12:49 "Re: [Tiff] Suggested Source Changes for Building libtiff Under Windows", by Frank Warmerdam
2007.06.29 18:18 "Re: [Tiff] Suggested Source Changes for Building libtiff Under Windows", by Kevin Myers
2007.06.29 13:12 "Re: [Tiff] Suggested Source Changes for Building libtiff Under Windows", by Andrey Kiselev
2007.06.29 19:58 "Re: [Tiff] Suggested Source Changes for Building libtiff Under Windows", by Kevin Myers
2007.06.30 07:29 "Re: [Tiff] Suggested Source Changes for Building libtiff Under Windows", by Kevin Myers
2007.06.29 15:17 "Re: [Tiff] Suggested Source Changes for Building libtiff Under Windows", by Bob Friesenhahn

2007.06.29 15:17 "Re: [Tiff] Suggested Source Changes for Building libtiff Under Windows", by Bob Friesenhahn

On Fri, 29 Jun 2007, Kevin Myers wrote:

>
> 8. Add a port.h header file for modules located in the port subdirectory.
>

> Since configuration level handling of header files are already > required for any module that makes use of a function that may be

> compiled under the port directory, it might make sense to consider > adding a port.h header file, and putting logic in the individual

> files that reference these functions to reference port.h rather than > the corresponding standard header file when appropriate. Might be

> cleaner than using the currently implemented external function > reference approach. Just something to consider...

I noticed this deficiency. It is certainly valuable to supply a port.h header file which offers the needed prototypes. In fact, the code may misbehave without it.

Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/