Re: [Openexr-devel] Chromaticity Attribute from C Interface

[Drew Hess]

OK, so sounds like we'll be able to continue supporting VC6 with the C
interface.  A heads-up to VC6 users, though: we are planning on
removing the VC6 project files from this next release.  This will only
affect you if you are building OpenEXR from scratch with VC6 and
Intel's C++ compiler.  We don't have a copy of the Intel C++ compiler
anymore and we don't have the time to build and test multiple Win32
targets.

d


"Luc-Eric Rousseau" <address@hidden> writes:

> It's fine, through the C interface
> objects are not allocated on one 
> side and freed on the other, and C run-time 
> objects like "FILE*" are not passed around.
> Every VC++ 6.0 developer has to deal sooner
> or later with dotNet-compiled shared libraries.
>
>> -----Original Message-----
>> From: Drew Hess [mailto:address@hidden
>> Sent: Tuesday, February 15, 2005 1:11 AM
>> To: Florian Kainz
>> Cc: address@hidden; Arnie Cachelin
>> Subject: Re: [Openexr-devel] Chromaticity Attribute from C Interface
>> 
>> 
>> 
>> I *think* that people who still want to use VC6 will be able to, as
>> long as somebody else compiles the release for them (with .NET 2003 or
>> whatever).
>> 
>> I'm not absolutely certain, though, because I'm not sure what will
>> happen when the OpenEXR libs, which will have been compiled against
>> .NET 2003's C++ runtime, are linked into an app that uses VC6's C++
>> runtime.
>> 
>> Any Windows experts out there know for sure?
>> 
>> 
>> d
>
>
> _______________________________________________
> Openexr-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/openexr-devel

pgpdZGnBWoco4.pgp
Description: PGP signature