- 2008.12.18 04:56 "[Tiff] tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
-
2008.12.18 21:56 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
-
2008.12.18 19:04 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Lee Howard
- 2008.12.18 19:18 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Edward Lam
-
2008.12.18 19:20 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
-
2008.12.18 19:28 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Lee Howard
- 2008.12.18 19:35 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Frank Warmerdam
- 2008.12.18 20:42 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Bob Friesenhahn
-
2008.12.18 19:28 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Lee Howard
- 2008.12.18 22:05 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Bob Friesenhahn
- 2008.12.21 16:03 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Jay Berkenbilt
-
2008.12.18 19:04 "Re: [Tiff] 3.9.0 release, Was: tiffvers.h - TIFFLIB_RELEASE macro addition", by Lee Howard
-
2009.01.21 04:07 "[Tiff] libtiff 4.0.0beta3", by Frank Warmerdam
-
2009.01.21 21:11 "Re: [Tiff] libtiff 4.0.0beta3", by Edward Lam
-
2009.01.22 16:23 "Re: [Tiff] libtiff 4.0.0beta3", by Edward Lam
- 2009.01.22 16:31 "Re: [Tiff] libtiff 4.0.0beta3", by Bob Friesenhahn
- 2009.01.22 17:00 "Re: [Tiff] libtiff 4.0.0beta3", by Bob Friesenhahn
- 2009.01.22 19:38 "Re: [Tiff] libtiff 4.0.0beta3", by Frank Warmerdam
-
2009.01.22 16:23 "Re: [Tiff] libtiff 4.0.0beta3", by Edward Lam
-
2009.01.21 21:11 "Re: [Tiff] libtiff 4.0.0beta3", by Edward Lam
- 2009.01.22 07:15 "[Tiff] Bugzilla not available?", by Rob Eisink
-
2009.02.05 18:38 "[Tiff] assertions, and building with DEBUG/NDEBUG", by Frank Warmerdam
- 2009.02.05 19:04 "Re: [Tiff] assertions, and building with DEBUG/NDEBUG", by Edward Lam
-
2009.02.05 19:13 "Re: [Tiff] assertions, and building with DEBUG/NDEBUG", by Bob Friesenhahn
- 2009.02.05 19:26 "Re: [Tiff] assertions, and building with DEBUG/NDEBUG", by Frank Warmerdam
- 2009.02.06 10:07 "Re: [Tiff] assertions, and building with DEBUG/NDEBUG", by
- 2009.02.06 10:44 "Re: [Tiff] assertions, and building with DEBUG/NDEBUG", by
- 2009.02.26 22:44 "Re: [Tiff] assertions, and building with DEBUG/NDEBUG", by
- 2009.02.07 14:10 "Re: [Tiff] The OJPEG bug 1996", by
2008.12.18 16:16 "Re: [Tiff] tiffvers.h - TIFFLIB_RELEASE macro addition", by Bob Friesenhahn
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.
Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/