summaryrefslogtreecommitdiffstats
path: root/release_docs
diff options
context:
space:
mode:
Diffstat (limited to 'release_docs')
-rwxr-xr-xrelease_docs/INSTALL_Windows_From_Command_Line.txt42
-rwxr-xr-xrelease_docs/INSTALL_Windows_Short_INTEL.TXT13
-rwxr-xr-xrelease_docs/INSTALL_Windows_Short_MSVS6.0.TXT12
-rwxr-xr-xrelease_docs/INSTALL_Windows_Short_NET.TXT2
4 files changed, 50 insertions, 19 deletions
diff --git a/release_docs/INSTALL_Windows_From_Command_Line.txt b/release_docs/INSTALL_Windows_From_Command_Line.txt
index 7572a24..33498aa 100755
--- a/release_docs/INSTALL_Windows_From_Command_Line.txt
+++ b/release_docs/INSTALL_Windows_From_Command_Line.txt
@@ -185,11 +185,16 @@ Section I: Building and testing HDF5 on command line with Microsoft
Invoke a command prompt window and run hdf5check with
appropriate options.
- Test results are saved into file:
+ Test results are saved in two files:
- c:\MyHDFstuff\hdf5\check_results.txt.
-
- Check check_results.txt and there should be failers at all.
+ c:\MyHDFstuff\hdf5\tests_results.txt
+
+ c:\MyHDFstuff\hdf5\check_results.txt.
+
+ In general, you only need to check tests_results.txt. If all the
+ tests passed, then you do not have to check check_results.txt.
+ If some tests failed, check check_results.txt can help you
+ figure out what was wrong.
3. Installing HDF5 Libraries
@@ -235,7 +240,8 @@ SECTION II: Building and testing HDF5 C and C++ Library on command line
1.5 Convert project files format from MSVS 6.0 to MSVS .Net
- Go to directory c:\MyHDFstuff\hdf5 and run convert_to_vcproj.bat
+ Go to directory c:\MyHDFstuff\hdf5 and run convert_to_vcproj.bat
+ in the following format
convert_to_vcproj "Absolute path of directory hdf5"
@@ -247,7 +253,7 @@ SECTION II: Building and testing HDF5 C and C++ Library on command line
the directory c:\MyHDFstuff\hdf5. The messages should look like
Converting: c:\MyHDFstuff\hdf5\windows\proj\all\all.dsp
- New Project Name: c:\MyHDFstuff\\hdf5\windows\proj\all\all.vcproj
+ New Project Name: c:\MyHDFstuff\hdf5\windows\proj\all\all.vcproj
Note: all.sln was provided with HDF5-1.8.0 Release. Users don't need
to convert the workspace from MSVS 6.0 format to MSVS .Net
@@ -321,8 +327,16 @@ SECTION II: Building and testing HDF5 C and C++ Library on command line
Note: hdf5check.bat has ONLY TWO options listed above in this case.
- Testing results will be saved in c:\MyHDFstuff\hdf5\check_results.txt.
- There should be no failures at all.
+ Test results are saved in two files:
+
+ c:\MyHDFstuff\hdf5\tests_results.txt
+
+ c:\MyHDFstuff\hdf5\check_results.txt.
+
+ In general, you only need to check tests_results.txt. If all the
+ tests passed, then you do not have to check check_results.txt.
+ If some tests failed, check check_results.txt can help you
+ figure out what was wrong.
3. Installing HDF5 Libraries
@@ -470,8 +484,16 @@ SECTION III: Building and testing HDF5 C and C++ Library on command
Notes: hdf5check.bat has ONLY TWO options listed above in this
case.
- Testing results will be saved in c:\MyHDFstuff\hdf5\check_results.txt.
- There should be no failures at all.
+ Test results are saved in two files:
+
+ c:\MyHDFstuff\hdf5\tests_results.txt
+
+ c:\MyHDFstuff\hdf5\check_results.txt.
+
+ In general, you only need to check tests_results.txt. If all the
+ tests passed, then you do not have to check check_results.txt.
+ If some tests failed, check check_results.txt can help you
+ figure out what was wrong.
3. Installing HDF5 Libraries
diff --git a/release_docs/INSTALL_Windows_Short_INTEL.TXT b/release_docs/INSTALL_Windows_Short_INTEL.TXT
index fbbc09e..e510e74 100755
--- a/release_docs/INSTALL_Windows_Short_INTEL.TXT
+++ b/release_docs/INSTALL_Windows_Short_INTEL.TXT
@@ -239,9 +239,16 @@ Part II. INTEL compiler 8.1 with Visual C++ .Net 2003 Environment
hdf5check enablecpp
- Test results will be save into file check_results.txt under
- directory "hdf5". Check check_results.txt, there should be no
- "failures" at all.
+ Test results are saved in two files:
+
+ c:\MyHDFstuff\hdf5\tests_results.txt
+
+ c:\MyHDFstuff\hdf5\check_results.txt.
+
+ In general, you only need to check tests_results.txt. If all the
+ tests passed, then you do not have to check check_results.txt.
+ If some tests failed, check check_results.txt can help you
+ figure out what was wrong.
b. Test HDF5 Static Fortran Library
diff --git a/release_docs/INSTALL_Windows_Short_MSVS6.0.TXT b/release_docs/INSTALL_Windows_Short_MSVS6.0.TXT
index ed06b64..d2db043 100755
--- a/release_docs/INSTALL_Windows_Short_MSVS6.0.TXT
+++ b/release_docs/INSTALL_Windows_Short_MSVS6.0.TXT
@@ -104,14 +104,16 @@ hdf5check.bat has four options:
Invoke a command prompt window and run hdf5check with appropriate
options.
-Test results are saved into file:
+Test results are saved in two files:
- c:\MyHDFstuff\hdf5\check_results.txt.
+ c:\MyHDFstuff\hdf5\tests_results.txt
-Check check_results.txt and there should be no failures at all.
+ c:\MyHDFstuff\hdf5\check_results.txt.
-If you want to test HDF5 libraries and tools one by one, please refer to
-Section II, step 2 in INSTALL_Windows.txt.
+In general, you only need to check tests_results.txt. If all the
+tests passed, then you do not have to check check_results.txt.
+If some tests failed, check check_results.txt can help you
+figure out what was wrong.
STEP 3: Installing HDF5 Libraries
diff --git a/release_docs/INSTALL_Windows_Short_NET.TXT b/release_docs/INSTALL_Windows_Short_NET.TXT
index 8edea56..f302737 100755
--- a/release_docs/INSTALL_Windows_Short_NET.TXT
+++ b/release_docs/INSTALL_Windows_Short_NET.TXT
@@ -41,7 +41,7 @@ Preconditions:
Invoke Microsoft Visual C++ .Net and go to "Tools" and select
"Options". In the left pane of "Option" window poped up,
- choose and extend "Projects", Click on "VC++ Directories".
+ choose and expand "Projects", Click on "VC++ Directories".
In the right pane, Find the box "Show directories for", choose
"Include files", if you can not find your Zlib and Szip
header path