RE: [Openexr-devel] OpenEXR 1.6.0, library issues under Windows

[Luc-Eric Rousseau]

This sounds like a problem with the way your work is setup.
The difference between a Debug and Release builds should only be the
compilation flags, including the path where to get the libraries.
The list of files and dependencies should normally be the same for all
configurations. 

Having different names for .lib and .dll between Debug and Release is
indeed one way to work, but there is no advantages to that, and
there are disadvantages in maintenance of makefiles and setups, and build
machines.  It's just not how things are done in most places.

You're supposed to specify a different library directory for Debug
and Release configuration in the linker options http://tinyurl.com/23fp54 
Perhaps you are using a global Library path in the user preference and
put both the Debug and Release .lib in the same directory, which you shouldn't
be doing.   When there are different Debug and Release versions of a library,
you need to specify the directory as part of the configuration of the Visual
Studio project.

In the same way, you're supposed to produce your Debug and Release executables
in different folders, along with the appropriate Debug and Release
third-party .dlls


-----Original Message-----
From: Ben Ochoa
Sent: Fri 8/24/2007 1:14 PM
To: address@hidden
Subject: [Openexr-devel] OpenEXR 1.6.0, library issues under Windows

I've been using OpenEXR 1.4.0 in Windows applications for the past year
and just tried OpenEXR 1.6.0.  I'm encountering some issues using the
1.6.0 libraries in my applications due to conflicting release and debug
libraries.  I believe that a different directory structure and file
naming convention would resolve these issues.

For OpenEXR 1.4.0, I use the `pre-compiled for Windows, Visual Studio
.NET 2005' package.  The 1.4.0 pre-compiled package placed the .lib and
.dll files in the lib and bin directories, and named the files according
to the four possible library configurations (e.g., for Half, there is
Half.lib (static release), Half_d.lib (static debug), Half_dll.lib and
Half_dll.dll (DLL release), and Half_dll_d.lib and Half_dll_d.dll (DLL
debug).  For my applications, I always linked to either the static or
static debug libraries for the respective release or debug build of my
applications.

Since a similar pre-compiled package is not currently available for
OpenEXR 1.6.0, I compiled it from source using the vc8 solution.
Compiling 1.6.0 from source only provides configurations for creating
DLLs.  Although it creates debug and release libraries in different
directories, the file names are the same (e.g., for Half, there is
lib\Release\Half.lib and bin\Release\Half.dll (DLL), and
lib\Debug\Half.lib and \bin\Debug\Half.dll (DLL debug).  It would be
great if the solution could be modified to create a directory structure
and file naming convention similar to 1.4.0, doing away with the Release
and Debug subdirectories, and placing both debug and release files in
the bin and lib directories, but with different names.  It would be nice
if the solution also contained configurations for building debug and
release static libraries, again placing them in the same bin and lib
directories.

I don't know Visual Studio well enough to make these changes myself, but
perhaps someone else does.  Would anyone else benefit from these changes?

Thanks,
Ben


_______________________________________________
Openexr-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/openexr-devel