AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
June 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



Valid HTML 4.01!



Thread

2010.06.17 15:39 "libtiff 4 API/ABI stability?", by Adam Goode
2010.06.17 16:21 "Re: libtiff 4 API/ABI stability?", by Edward Lam
2010.06.17 16:22 "Re: libtiff 4 API/ABI stability?", by Edward Lam
2010.06.17 16:38 "Re: libtiff 4 API/ABI stability?", by Adam Goode
2010.06.17 22:06 "Re: libtiff 4 API/ABI stability?", by Edward Lam
2010.06.18 00:13 "Re: libtiff 4 API/ABI stability?", by Adam Goode
2010.06.18 13:44 "Re: libtiff 4 API/ABI stability?", by Edward Lam
2010.06.18 17:46 "[PATCH] Build tif_win32.c on Windows except on Cygwin", by Adam Goode
2010.06.18 18:21 "Re: [PATCH] Build tif_win32.c on Windows except on Cygwin", by Bob Friesenhahn
2010.06.18 18:32 "Re: [PATCH] Build tif_win32.c on Windows except on Cygwin", by Adam Goode
2010.06.18 18:35 "Re: [PATCH] Build tif_win32.c on Windows except on Cygwin", by Adam Goode
2010.06.28 13:25 "Re: [PATCH] Build tif_win32.c on Windows except on Cygwin", by Edward Lam
2010.06.28 15:54 "Re: [PATCH] Build tif_win32.c on Windows except on Cygwin", by Bob Friesenhahn
2010.06.29 11:23 "Re: [PATCH] Build tif_win32.c on Windows except on Cygwin", by Andrey Kiselev
2010.06.29 13:46 "Re: [PATCH] Build tif_win32.c on Windows except on Cygwin", by Adam Goode
2010.06.17 16:28 "Re: libtiff 4 API/ABI stability?", by Bob Friesenhahn
2010.06.17 16:34 "Re: libtiff 4 API/ABI stability?", by Adam Goode
2010.06.17 16:55 "Re: libtiff 4 API/ABI stability?", by Bob Friesenhahn
2010.06.17 17:15 "Re: libtiff 4 API/ABI stability?", by Adam Goode
2010.06.17 18:04 "Re: libtiff 4 API/ABI stability?", by Olivier Paquet
2010.06.17 18:09 "Re: libtiff 4 API/ABI stability?", by Adam Goode
2010.06.17 18:47 "Re: libtiff 4 API/ABI stability?", by Bob Friesenhahn
2010.06.17 19:35 "Re: libtiff 4 API/ABI stability?", by Olivier Paquet
2010.06.18 00:33 "Re: libtiff 4 API/ABI stability?", by Adam Goode
2010.06.18 01:45 "Re: libtiff 4 API/ABI stability?", by Adam Goode
2010.06.18 01:54 "Re: libtiff 4 API/ABI stability?", by Olivier Paquet
2010.06.18 02:00 "Re: libtiff 4 API/ABI stability?", by Adam Goode
2010.06.18 13:32 "Re: libtiff 4 API/ABI stability?", by Edward Lam
2010.06.18 13:54 "Re: libtiff 4 API/ABI stability?", by Olivier Paquet
2010.06.18 02:36 "Re: libtiff 4 API/ABI stability?", by Bob Friesenhahn
2010.06.17 20:14 "Re: libtiff 4 API/ABI stability?", by Tom Lane
2010.06.17 20:35 "Re: libtiff 4 API/ABI stability?", by Bob Friesenhahn
2010.06.18 00:31 "Re: libtiff 4 API/ABI stability?", by Adam Goode

2010.06.18 00:13 "Re: libtiff 4 API/ABI stability?", by Adam Goode

On 06/17/2010 06:06 PM, Edward Lam wrote:
> Sorry, I think that I'm wrong on this. It does look like tif_win32.c is
> the default. On the note of tif_unix.c for Windows, I think we only need
> to patch it _lseeki64 to work for large files?
> 

It is the default if you use Makefile.vc. If you use the standard
configure and make (like with MinGW), then tif_unix.c is used. And yes,
it looks like _lseeki64 is all that is needed here. Though in that case,
you don't get mmap on Windows.

I could put together a patch to the autotools stuff to pick tif_win32.c
on Windows. Then we just need to fix bug 1941.



Adam