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
December 2008

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

2008.12.18 04:56 "tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
2008.12.18 05:13 "Re: tiffvers.h - TIFFLIB_RELEASE macro addition", by Lee Howard
2008.12.18 05:31 "Re: tiffvers.h - TIFFLIB_RELEASE macro addition", by Bob Friesenhahn
2008.12.18 06:00 "Re: tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
2008.12.18 16:16 "Re: tiffvers.h - TIFFLIB_RELEASE macro addition", by Bob Friesenhahn
2008.12.18 18:59 "Re: tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
2008.12.18 19:04 "Re: 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Lee Howard
2008.12.18 19:18 "Re: 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Edward Lam
2008.12.18 19:20 "Re: 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
2008.12.18 19:28 "Re: 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Lee Howard
2008.12.18 19:35 "Re: 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
2008.12.18 20:11 "Re: 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
2008.12.18 20:42 "Re: 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Bob Friesenhahn
2008.12.18 21:56 "Re: 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
2008.12.18 22:05 "Re: 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Bob Friesenhahn
2008.12.19 02:26 "Re: 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
2008.12.19 03:12 "Re: 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Bob Friesenhahn
2008.12.21 16:03 "Re: 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Jay Berkenbilt
2008.12.21 16:10 "Re: 3.9.0 release", by Jay Berkenbilt
2008.12.21 15:35 "Re: 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Jay Berkenbilt
2008.12.21 15:57 "Re: 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Jay Berkenbilt
2008.12.21 16:14 "Re: 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
2008.12.21 16:44 "Re: 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Jay Berkenbilt

2008.12.18 18:59 "Re: tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam

Bob Friesenhahn wrote:
> On Thu, 18 Dec 2008, Frank Warmerdam wrote:
>>>
>>> The available values are CURRENT, REVISION, and AGE in order of 
>>> decreasing significance.  For example, CURRENT might be 4.
>>
>> But this is not normally conveniently available to applications building
>> against libtiff, right?  It requires some sort of configure magic to
>> extract the libtool versioning and represent it as macros passed into
>> the application. It wouldn't do anything for someone on windows for
>> instance.
> 
> Right.  That is where the substitution magic which builds tiffvers.h 
> comes in.  Then the versioning info is available to all.  It is not 
> difficult for configure/make to maintain a continually up to date 
> tiffvers.h.
> 
>>> The approach you describe still only works if the major release 
>>> update always offers additional features over the previous major 
>>> release.
>>
>> I do not understand this comment.
> 
> What I mean is your use of arbitrary libtiff version numbers to 
> determine if a feature is available.  Features can be backported and it 
> is even possible that a lesser numbered library supports a feature which 
> is not available in a higher numbered library.

Folks,

OK, I'm finding interest in TIFFLIB_RELEASE lukewarm at best, and I
have decided against going ahead with it.  I'll leave things as they are
in this regard.  For my own purposes I already need to detect whether
I have BigTIFF support, so I'll just use TIFFUnsetField() if the date is
later than a particular date, and if I have bigtiff support.

Best regards,
-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent