Hi, On Tue, Nov 20, 2012 at 10:15 AM, saracaeus <[email protected]> wrote:
> There are 2 HDF5 libraries: hdf5-1.6.4_d.lib (debug version) and > hdf5-1.6.4.lib (release version). I use the debug version for my sample > program which is compiled in debug mode. So this shouldnt be the problem. > And it wouldn't explain, why the statically linked MFC library is working > while the dll MFC version is not. > > But in the end the program will run under Linux, using Qt... The sample > program is meant to make first steps in HDF5. So I dont think I will have > the same probs in the final release :) > It's not just debug vs. release. You also have to look at the underlying C runtime, which should be the same for all libraries and executables. You can see what a particular library or program uses by executing "dumpbin /imports <program>" from a Visual Studio command prompt. Each one should be linked to the same MSVCR#.dll. The problem is that Windows implements the C library calls in separate dlls, which do not share state. Dana
_______________________________________________ Hdf-forum is for HDF software users discussion. [email protected] http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
