LibTiff Mailing List

On Tue, 30 Nov 2010, Kevin Myers wrote:

> I haven't looked into this very much *at all*, so what I am about to say
> could easily be *very* wrong.  That being said, wouldn't changing libtiff to
> use read() and write() break large file handling (greater than 4GB) under
> Win32?  If so, that would be a bad thing.

It is possible to use read() and write() with large files under 
Windows.  GraphicsMagick does so.  It works with Visual C++ but last 
time I tried with MinGW GCC it did not work because MinGW was not 
enabling the necessary APIs.

As far as libtiff using Windows file APIs goes, it can be "cured" by 
using TIFFClientOpen() to specify use of the desired file access APIs. 
This requires writing some tiny I/O wrapper functions.

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


AWARE [SYSTEMS]		Imaging expertise for the Delphi developer
		TIFF and LibTiff Mailing List Archive
	LibTiff Mailing List TIFF and LibTiff Mailing List Archive November 2010 Previous Thread Next Thread Previous by Thread Next by Thread Previous by Date Next by Date Contact The TIFF Mailing List Homepage This list is run by Frank Warmerdam Archive maintained by AWare Systems	Thread 2010.11.30 19:15 "Win32 ReadFile() / WriteFile() heads-up", by John Emmas 2010.11.30 19:26 "Re: Win32 ReadFile() / WriteFile() heads-up", by Toby Thain 2010.11.30 19:58 "Re: Win32 ReadFile() / WriteFile() heads-up", by John Emmas 2010.11.30 20:08 "Re: Win32 ReadFile() / WriteFile() heads-up", by Toby Thain 2010.11.30 20:12 "Re: Win32 ReadFile() / WriteFile() heads-up", by Frank Warmerdam 2010.12.01 17:40 "Re: Win32 ReadFile() / WriteFile() heads-up", by John Emmas 2010.12.05 18:36 "Re: Win32 ReadFile() / WriteFile() heads-up", by Edward Lam 2010.11.30 19:43 "Re: Win32 ReadFile() / WriteFile() heads-up", by Kevin Myers 2010.12.01 05:15 "Re: Win32 ReadFile() / WriteFile() heads-up", by Bob Friesenhahn 2010.12.01 08:45 "Re: Win32 ReadFile() / WriteFile() heads-up", by John Emmas 2010.12.01 06:35 "Re: Tiff Digest, Vol 79, Issue 1 - Win32 ReadFile() / WriteFile() heads-up (John Emmas)", by David J Taylor 2010.12.01 12:37 "Re: Win32 ReadFile() / WriteFile() heads-up", by Phil Harvey 2010.12.05 18:05 "Re: Win32 ReadFile() / WriteFile() heads-up", by Edward Lam 2010.12.01 05:15 "Re: Win32 ReadFile() / WriteFile() heads-up", by Bob Friesenhahn On Tue, 30 Nov 2010, Kevin Myers wrote: > I haven't looked into this very much at all, so what I am about to say > could easily be very wrong. That being said, wouldn't changing libtiff to > use read() and write() break large file handling (greater than 4GB) under > Win32? If so, that would be a bad thing. It is possible to use read() and write() with large files under Windows. GraphicsMagick does so. It works with Visual C++ but last time I tried with MinGW GCC it did not work because MinGW was not enabling the necessary APIs. As far as libtiff using Windows file APIs goes, it can be "cured" by using TIFFClientOpen() to specify use of the desired file access APIs. This requires writing some tiny I/O wrapper functions. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/

LibTiff Mailing List

Thread

2010.12.01 05:15 "Re: Win32 ReadFile() / WriteFile() heads-up", by Bob Friesenhahn