Return-Path: <tiff-bounces@lists.maptools.org>
Received: from inas011.isp.belgacom.be (localhost [127.0.0.1])
        by inav011.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AV-3.00) with ESMTP id j7OKAJv1021532
        for <joris.at.lebbeke@skynet.be>; Wed, 24 Aug 2005 22:10:19 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from inmx002.isp.belgacom.be (inmx002.isp.belgacom.be [195.238.3.7])
        by inas011.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AS-2.03) with ESMTP id j7OKAEbc014136
        for <joris.at.lebbeke@skynet.be>; Wed, 24 Aug 2005 22:10:14 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (r153.dmsolutions.ca [209.217.116.153] (may be forged))
        by inmx002.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id j7OKA9DR017461
        for <joris.at.lebbeke@skynet.be>; Wed, 24 Aug 2005 22:10:09 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (duke.maptools.org [127.0.0.1])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id j7OK42RG014421;
	Wed, 24 Aug 2005 16:05:06 -0400
Received: from cgp.spb.edu (vlan3.cgp.spb.edu [195.70.196.207])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id j7OK3xfI014418
	for <tiff@lists.maptools.org>; Wed, 24 Aug 2005 16:04:00 -0400
Received: from wg.pu.ru ([193.124.85.219] verified)
	by cgp.spb.edu (CommuniGate Pro SMTP 4.3c5)
	with ESMTP id 9267039 for tiff@lists.maptools.org;
	Thu, 25 Aug 2005 00:01:10 +0400
Received: (from uucp@localhost)
	by wg.pu.ru (8.9.1a/8.9.1) with UUCP id UAA24481
	for tiff@lists.maptools.org; Wed, 24 Aug 2005 20:03:56 GMT
Received: from ak4719.spb.edu (localhost [127.0.0.1])
	by ak4719.spb.edu (8.13.4/8.13.4/Debian-3) with ESMTP id j7OJcF65013595
	for <tiff@lists.maptools.org>; Wed, 24 Aug 2005 23:38:15 +0400
Received: (from dron@localhost)
	by ak4719.spb.edu (8.13.4/8.13.4/Submit) id j7OJcFB0013591
	for tiff@lists.maptools.org; Wed, 24 Aug 2005 23:38:15 +0400
From: Andrey Kiselev <dron@ak4719.spb.edu>
Date: Wed, 24 Aug 2005 23:38:15 +0400
To: tiff@lists.maptools.org
Subject: Re: [Tiff] win32 libtiff
Message-ID: <20050824193815.GB11500@ak4719.spb.edu>
Mail-Followup-To: tiff@lists.maptools.org
References: <20050824181016.GA2637@ak4719.spb.edu>
	<200508241923.j7OJNVTC010899@mailhub131.itcs.purdue.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200508241923.j7OJNVTC010899@mailhub131.itcs.purdue.edu>
X-GnuPG-Key: http://www.srces.spb.org/dron/export.home.key
X-Face: "t+se9s~+y~[XUH]L|pmeO3Pt/Q@DNv**S, d@_1-C=}/,
	c%<3Qp]eu!ok<"2lYJm$!9qVcg F?7o*L; |$`6|Q|>Rt-cU%2_y@6tQ|`!Li}TsvZvEKx;
	>fuY=fc(=sX^`7Wmw8%SsR`AvM$a; 0U/eN\ P?B\FTyqD, 0np$U2!*'z_4D,
	VPlFf?bN0&zYf"zF0s!7Tl7?$we)xD0@lL>[h|8bhys0i.g|zLnu@C
	Ti@d]i=[!:j1CB\5/TF[m]`lfHfaqSN[0qn@T3zeosV/[LAss{@p_?],x*j8P_9t[}uHD^X-;
	j~\M! gyTly;fj`}&Y~i{<#bN.#QmkE}#T`dxP.I1\.)_MEN{@#W
User-Agent: Mutt/1.5.9i
X-Virus-Scanned: ClamAV 0.84/1038/Wed Aug 24 02:45:29 2005 on ak4719
X-Virus-Status: Clean
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=subscribe>
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org
X-UIDL: 000000000023ceae.00000b3f
X-MSP-STORE: Wed, 24 Aug 2005 22:10:24 +0200
Status:   

On Wed, Aug 24, 2005 at 02:23:40PM -0500, Mark R. Olin wrote:
> I did some footwork before downloading libtiff, since I anticipated
> that there might be issues with win32 vs. unix versions.  If you go to
> the following page
> 
> http://gnuwin32.sourceforge.net/packages/tiff-win32.htm ,

That is not a home of libtiff, but rather a home of one of the win32
library builds.

> The GnuWin32 distribution comes in two versions. The ordinary version
> uses the standard Unix equivalents, such as fopen and read, for input
> and output, the other version (Tiff-win32) uses the Win32 API
> functions, such as CreateFile and ReadFile, for input and output. The
> ordinary version (Tiff) is more suitable for porting Unix programs,
> the Win32-API version is more suitable for writing Win32 programs.

Modern libtiff can be built using different I/O interfaces. Both
open/read and OpenFile/ReadFile interfaces can be used in your build
(switched with the USE_WIN_CRT_LIB option in nmake.opt file). I am
recommend using open/read calls (USE_WIN_CRT_LIB is on). You can search
the mailing list archive for discussion on this topic.

> Homepage
> 
>  http://www.remotesensing.org/libtiff
> 
> (but as of this writing, the homepage link appears to be a broken link)

Huh, it doesn't work right now too! Problem with our server again...

> Andrey, may I assume from your question/statements below that I can
> begin using the 3.7.3 distribution for use with win32 compilers?

You definetely should use the latest version, because 3.6.1 is quit old.

Andrey


-- 
Andrey V. Kiselev
Home phone:  +7 812 5970603  ICQ# 26871517
_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
