[Bf-committers] libtiff linking

[Damien Plisson]

Quicktime provides support for tiff only for reading.
Libtiff dyn lib is thus still needed to be installed on OSX for getting tiff write support.

FYI, I added the write support a while ago, but following a discussion with Matt, I reverted it. The main issue was that all platforms need to provide 100% exactly same rendering (i.e. colorimetry, ...), and so all platforms has to use libtiff and no other tiff interpreter. Especially important on a multiplatform production environment.

Damien

Le 19 avr. 2010 à 15:19, Campbell Barton a écrit :

> quicktime/tiff wouldn't support tiff mipmap's and tiling so we could
> include on all OS's now.
> Wait until Brecht merges his mipmap commit into trunk before attempting.
> 
> On Mon, Apr 19, 2010 at 2:23 PM, Jonathan Merritt
> <merritt at unimelb.edu.au> wrote:
>> On Mon, 2010-04-19 at 19:30 +1000, Matt Ebb wrote:
>>> On Mon, Apr 19, 2010 at 7:20 PM, Campbell Barton <ideasman42 at gmail.com> wrote:
>>>> Is there any reason we still dynamically load libtiff?, Why don't we
>>>> static link like OpenEXR, or link normally as we do with libjpeg.
>>> 
>>> I could be wrong, but from memory there were concerns about the size
>>> of the library when it was first introduced.. But it seems to be
>>> linked statically here on osx anyway, with no big problem really.
>> 
>> Spot on - at the time, libtiff was mainly required for Linux, since
>> QuickTime was handling TIFF under OSX and Windows.  I wrote the dynamic
>> load and stub methods, and needed a lot of help for the
>> platform-specific library detection.  I would love to see all that
>> disappear in favour of normal linking (static or dynamic). :-)