[Radiance-dev] libtiff in Linux radiance

[Randolph Fritz]

(Sorry it's taken so long to get back to you on this)

Looks to me like you could just compile and link a small test program 
which references libtiff and TIFFInitSGILog()--if it builds, libtiff 
with logluv support is in a default library directory. I think that's 
sufficient. If you want something more specific, I could work out a 
script that would identify the system's type and queries the package 
manager for specific file locations, but it seems like overkill to me.

Randolph

Gregory J. Ward wrote:
> That's kind of what I was thinking.  Create different targets and 
> stuff the appropriate one in the rmake script via makeall.  Still need 
> a reliable way to determine (on any distro) the location and contents 
> of the tiff library.  If I can find the location, I can probably use 
> the nm command to look up the symbols and check that they're defined.
>
> -Greg
>
>> From: R Fritz <rfritz at u.washington.edu>
>> Date: December 17, 2008 3:44:04 PM PST
>>
>> Could the test could be done in the makeall script, and the result 
>> used in Makefiles?
>>
>> Randolph
>>
>> On Dec 16, 2008, at 7:45 PM, Gregory J. Ward wrote:
>>
>>> Hi Randolph,
>>>
>>> Do you think there's a way to do this with Makefile's?  One way I 
>>> can think to do it is to modify the tiff target I used to have into 
>>> separate targets for the local or system library.  What technique 
>>> did you use to detect the presence of a libtiff with LogLuv support?
>>>
>>> -Greg
>>>
>>>> From: R Fritz <rfritz at u.washington.edu>
>>>> Date: December 16, 2008 6:22:34 PM PST
>>>>
>>>> One of the things I tried in my experimental Radiance build scripts 
>>>> was testing for the presence of a system libtiff with logluv 
>>>> support and using it.  Is that something that's planned for 4.0?
>>>>
>>>> Randolph
>
> _______________________________________________
> Radiance-dev mailing list
> Radiance-dev at radiance-online.org
> http://www.radiance-online.org/mailman/listinfo/radiance-dev