summaryrefslogtreecommitdiffstats
path: root/release_docs/INSTALL_Windows.txt
diff options
context:
space:
mode:
authorScott Wegner <swegner@hdfgroup.org>2007-08-03 14:44:44 (GMT)
committerScott Wegner <swegner@hdfgroup.org>2007-08-03 14:44:44 (GMT)
commite2477c8d0b76325590f43be8926634f16da5f849 (patch)
tree9f73c547c447d6af4efc0c9dddcea619a3269aa0 /release_docs/INSTALL_Windows.txt
parent7f2265149224ffa99b7a9825d4faf0b4823f4562 (diff)
downloadhdf5-e2477c8d0b76325590f43be8926634f16da5f849.zip
hdf5-e2477c8d0b76325590f43be8926634f16da5f849.tar.gz
hdf5-e2477c8d0b76325590f43be8926634f16da5f849.tar.bz2
[svn-r14036] Purpose: Fix Windows debug DLL naming scheme
Description: At a previous seminar, it was brought up that the naming scheme for Windows debug DLL is inconsistent. Specifically, some use *ddll, while others use *dlld. *dlld is more widely-used, so we decided this is "correct". This changes others to use this scheme, and adapts other projects / install scripts / documentation. Tested: Visual Studio .NET on WinXP
Diffstat (limited to 'release_docs/INSTALL_Windows.txt')
-rw-r--r--release_docs/INSTALL_Windows.txt20
1 files changed, 10 insertions, 10 deletions
diff --git a/release_docs/INSTALL_Windows.txt b/release_docs/INSTALL_Windows.txt
index 466a5fe..5994cb2 100644
--- a/release_docs/INSTALL_Windows.txt
+++ b/release_docs/INSTALL_Windows.txt
@@ -361,8 +361,8 @@ STEP 1: Building HDF5 Libraries and Tools
c:\MyHDFstuff\hdf5\proj\hdf5_cppdll\debug -
- hdf5_cppdlld.dll- the HDF5 C++ API DLL
- hdf5_cppdlld.lib - the C++ API export library
+ hdf5_cppddll.dll- the HDF5 C++ API DLL
+ hdf5_cppddll.lib - the C++ API export library
and c:\MyHDFstuff\hdf5\proj\hdf5_cppdll\release -
@@ -386,8 +386,8 @@ STEP 1: Building HDF5 Libraries and Tools
and c:\MyHDFstuff\hdf5\proj\hdf5_hldll\Debug -
- hdf5_hldlld.dll - HDF5 High Level DLL
- hdf5_hldlld.lib - HDF5 High Level export Library
+ hdf5_hlddll.dll - HDF5 High Level DLL
+ hdf5_hlddll.lib - HDF5 High Level export Library
The directories listed below will contain the following files
ONLY when you choose to build HDF5 High Level C++ libraries:
@@ -403,8 +403,8 @@ STEP 1: Building HDF5 Libraries and Tools
c:\MyHDFstuff\hdf5\proj\hdf5_hl_cppdll\Release -
and c:\MyHDFstuff\hdf5\proj\hdf5_hl_cppdll\Debug -
- hdf5_hl_cppdlld.dll - HDF5 High Level C++ DLL
- hdf5_hl_cppdlld.lib - HDF5 High Level C++ export Library
+ hdf5_hl_cppddll.dll - HDF5 High Level C++ DLL
+ hdf5_hl_cppddll.lib - HDF5 High Level C++ export Library
STEP 2: Testing HDF5 Libraries and Tools
@@ -611,7 +611,7 @@ We provide 2 options for users to test HDF5 libraries and tools.
be copied to the system directory.
c:\MyHDFstuff\hdf5\proj\hdf5_hldll\Release\hdf5_hldll.dll
- c:\MyHDFstuff\hdf5\proj\hdf5_hldll\Debug\hdf5_hldlld.dll
+ c:\MyHDFstuff\hdf5\proj\hdf5_hldll\Debug\hdf5_hlddll.dll
Run test_hdf5_hl.bat in the hdf5\hl\test directory at the command prompt as
below:
@@ -642,7 +642,7 @@ We provide 2 options for users to test HDF5 libraries and tools.
will be copied to the system directory.
c:\MyHDFstuff\hdf5\proj\hdf5_hlcppdll\Release\hdf5_hlcppdll.dll
- c:\MyHDFstuff\hdf5\proj\hdf5_hlcppdll\Debug\hdf5_hlcppdlld.dll
+ c:\MyHDFstuff\hdf5\proj\hdf5_hlcppdll\Debug\hdf5_hlcppddll.dll
Run test_hdf5_hl_cpp.bat in the hdf5\hl\c++\test directory at the command
prompt as below:
@@ -673,9 +673,9 @@ We provide 2 options for users to test HDF5 libraries and tools.
DLLs will be copied to the system directory.
c:\MyHDFstuff\hdf5\proj\hdf5_hl_f90cstubdll\Release\hdf5_hl_f90cstubdll.dll
- c:\MyHDFstuff\hdf5\proj\hdf5_hl_f90cstubdll\Debug\hdf5_hl_f90cstubdlld.dll
+ c:\MyHDFstuff\hdf5\proj\hdf5_hl_f90cstubdll\Debug\hdf5_hl_f90cstubddll.dll
c:\MyHDFstuff\hdf5\proj\hdf5_hlfortrandll\Release\hdf5_hlfortrandll.dll
- c:\MyHDFstuff\hdf5\proj\hdf5_hlfortrandll\Debug\hdf5_hlfortrandlld.dll
+ c:\MyHDFstuff\hdf5\proj\hdf5_hlfortrandll\Debug\hdf5_hlfortranddll.dll
Run test_hdf5_hl_fortran.bat in the hdf5\hl\fortran\test directory at the
command prompt as below: