Re: [Openexr-devel] OpenEXR 1.0.5 released

[Drew Hess]

Hi Andreas,

I don't have much experience building Windows projects, as you can 
probably tell.  What do I need to do to the project file to link 
libmmd statically?  And zlib?  zlib makes a .lib file but I couldn't get 
exrdisplay and exrheader to work without having the zlib.dll in my path.  
Dunno why.

As for the runtime dlls (msvcp60.dll, msvcrt.dll are runtime dlls,
right?), the reason I made those dynamic is so that you can link OpenEXR
libs against other libs that are complied against the runtime dlls.  For
example, I had linking problems with fltk (which is built against the
runtime DLLs by default) until I switched.

Unless people tell me that most people use static runtime libs and that 
fltk is the exception, I think I'll keep the prebuilt libs dependent on 
the runtime DLLs.  People who want to use the statics can change the 
project options.

And no, it wasn't my intention to exclude the VS6.0 project files from the 
source tarball.  That's a mistake in the dist.  I'll update it today and 
let everyone know when it's fixed.  Linux and MacOS X users are unaffected 
by this and can use the source tarball as-is.


thanks for the feedback
-dwh-


 On Fri, 21 Mar 2003, Andreas Kahler wrote:

> Hi!
> 
> > OpenEXR-1.0.5.zip
> >    - binaries, headers, and prebuilt libs for Windows XP/2000.  The
> >      prebuilt libs require Visual Studio 6.0 and the Intel C++
> >      compiler version 7.0 for full C++ support, but you should be able to
> >      use the ImfCRgbaFile C interface with Microsoft Visual C++ 6.0 and
> the
> >      included IlmImf.dll.
> 
> Cool, this should make it much easier for MSVC++ users.
> 
> Unfortunately, IlmImf.dll doesn't work like intended. It has a dependency to
> libmmd.dll, which comes with the Intel compiler and is usually not installed
> on Windows systems. I don't know if libmmd.dll can be redistributed, but I
> think it's better to get rid of this dependency and link it statically.
> 
> It probably also would be a good idea to remove some of the other
> dependencies (zlib.dll, msvcp60.dll, msvcrt.dll). The less dependencies
> you have, the less problems you will have later when using it.
> 
> BTW: There are no MSVC++ project and workspace files included in the
> tar file. Is this by intention?
> 
> Andreas
> --
> Andreas Kahler, Project Manager Applications
> NXN Software AG, Sonnenstrasse 19, D-80331 Muenchen, Germany
>