Its all established in your %PATH%
E.g. PATH=%SystemRoot%\system32
%SystemRoot%
%SystemRoot%\System32\Wbem
C:\windows/Microsoft.NET/Framework/v2.0.50727
I have all three VS2003, VS2005, and VS2008 running and have had no DLL hell
issues.
Furthermore, I have built HDF5-1.8.2 with VS2008 and two applications to
read NASA Aura HE5 data.
I suggest you upgrade to at least VS2005.
John Huddleston, PhD
···
_____
From: Grant Tang [mailto:grant.tang@gmail.com]
Sent: Wednesday, February 04, 2009 11:23 AM
To: Francesc Alted
Cc: hdf-forum@hdfgroup.org
Subject: Re: [hdf-forum] Re: HDF5 ptoblem on WindowsXP
I checked with dependency walker. Exactly as you said, the hdf5dll.dll
linked to MSVCR80.dll:
c:\windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.3053_non
e_d08d7bba442a9b36\MSVCR80.DLL
I must figure out a way to "explicitly link your binaries against
msvcr71.dll (the CRT that comes
with VS2003) instead of the msvcr.dll that comes with VS2005."
Thanks for all feedback,
Grant
On Wed, Feb 4, 2009 at 1:24 AM, Francesc Alted <faltet@pytables.com> wrote:
A Tuesday 03 February 2009, Francesc Alted escrigué:
Grant,
There has been a recent discussion about similar problems in the
NumPy list. See:
http://projects.scipy.org/pipermail/numpy-discussion/2009-February/04
0053.html
Do you have VS2003 and VS2005 simultaneously installed in your
computer? If this is the case, you may have been bitten by the
different CRTs issue. When you are using VS2003, you should
explicitly link your binaries against msvcr71.dll (the CRT that comes
with CS2003) instead of the msvcr.dll that comes with VS2003.
Uh. I meant:
"""
explicitly link your binaries against msvcr71.dll (the CRT that comes
with VS2003) instead of the msvcr.dll that comes with VS2005.
"""
The consequences of writing too late :-/
However, if you can't manage to link against msvcr71.dll, you may
want to try another venue: compile with VS2005 and link with
msvcr.dll. Following Mr. Molden, you should be able to use different
MS compilers as long you always link with the appropriate CRT. I've
never tried this, but it makes sense to me.
HTH,
Francesc
A Tuesday 03 February 2009, Grant Tang escrigué:
> I checked the library hdf5dll.dll, there is a function H5Eget_auto
> in it. Actually I compiled EMAN with this library some time ago.
> And it works fine. But later on I installed Visual Studio 2005 on
> my computer. Now I have such strange run time problem with a
> previous working compilation. Not sure whether the VS2005 causes
> some conflict. Anybody?
> Grant
>
> On Mon, Feb 2, 2009 at 5:40 PM, Grant Tang <grant.tang@gmail.com> > > wrote:
> > Hi,
> > I compile my application EMAN with visual studio 2003 .Net, which
> > needs HDF5 1.6.5. The compilation process is fine. But when I try
> > to load my application, I got this error:
> >
> > "The procedure entry point H5Eget_auto could not be located in
> > the dynamic link library hdf5dll.dll"
> >
> > Could somebody help me?
> >
> >
> > --
> > Grant
--
Francesc Alted
----------------------------------------------------------------------
This mailing list is for HDF software users discussion.
To subscribe to this list, send a message to
hdf-forum-subscribe@hdfgroup.org.
To unsubscribe, send a message to hdf-forum-unsubscribe@hdfgroup.org.
--
Grant Tang
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.233 / Virus Database: 270.10.17/1933 - Release Date: 02/03/09
17:48:00