summaryrefslogtreecommitdiffstats
path: root/release_docs/INSTALL_Windows_From_Command_Line.txt
diff options
context:
space:
mode:
authorAllen Byrne <byrn@hdfgroup.org>2010-03-03 20:20:16 (GMT)
committerAllen Byrne <byrn@hdfgroup.org>2010-03-03 20:20:16 (GMT)
commitef844be70d9c85c1d6093a91283ce915f0351140 (patch)
treee6e83fe7de4c23157cc8bf9a28abe2c4c2496fe9 /release_docs/INSTALL_Windows_From_Command_Line.txt
parent483185409e16ec83c24301e21bfdc92234506730 (diff)
downloadhdf5-ef844be70d9c85c1d6093a91283ce915f0351140.zip
hdf5-ef844be70d9c85c1d6093a91283ce915f0351140.tar.gz
hdf5-ef844be70d9c85c1d6093a91283ce915f0351140.tar.bz2
[svn-r18360] Updated project files and release docs to VS2008 and IVF101 based.
Made change to cpp version of testhdf5 for the elimination of dsets standalone. Tested: Windows
Diffstat (limited to 'release_docs/INSTALL_Windows_From_Command_Line.txt')
-rwxr-xr-xrelease_docs/INSTALL_Windows_From_Command_Line.txt26
1 files changed, 12 insertions, 14 deletions
diff --git a/release_docs/INSTALL_Windows_From_Command_Line.txt b/release_docs/INSTALL_Windows_From_Command_Line.txt
index c35fdbf..771bcf0 100755
--- a/release_docs/INSTALL_Windows_From_Command_Line.txt
+++ b/release_docs/INSTALL_Windows_From_Command_Line.txt
@@ -5,12 +5,12 @@
Note: This instruction is written for users who would like to build HDF5
libraries and tools from the HDF5 source code package on command
line. We no longer support building HDF5 using Microsoft Visual
- Studio .NET 2003.
+ Studio 2005.
Currently, we support:
1. Building and testing HDF5 C/C++/Fortran libraries on command line with
- Microsoft Visual Studio 2005 or 2008 for 32- or 64-bit Windows.
+ Microsoft Visual Studio 2008 for 32- or 64-bit Windows.
For all other Windows development tools, HDF5 should be built in
the development environment. Please refer to INSTALL_Windows.txt
@@ -37,14 +37,12 @@ notes in INSTALL_Windows.txt before starting below procedures.
Studio. These are generally setup when Visual Studio is installed, but you
can verify by running the command:
- echo %vs80comntools%
+ echo %vs90comntools%
This should output a path similar to:
- C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\
-
- If you are using Visual Studio 2008, use "vs90comntools"
-
+ C:\Program Files\Microsoft Visual Studio 9\Common7\Tools\
+
1.2 Run batch file copy_hdf.bat.
Go to c:\MyHDFstuff\hdf5\windows and run copy_hdf.bat.
@@ -81,12 +79,10 @@ notes in INSTALL_Windows.txt before starting below procedures.
from command line.
hdf5bt file takes the following options:
- /vs8 Build HDF5 using Visual Studio 2005
/vs9 Build HDF5 using Visual Studio 2008
- Note: Default is Visual Studio 2005
/fort Build and test HDF5 with Fortran libraries
/ivf101 Build HDF5 Fortran using Intel Visual Fortran 10.1
- Note: Default is Intel Visual Fortran 9.1
+ /ivf111 Build HDF5 Fortran using Intel Visual Fortran 11.1
/useenv Build HDF5 using compiler settings defined
in the environment, rather than the IDE.
/? Help information
@@ -110,13 +106,12 @@ notes in INSTALL_Windows.txt before starting below procedures.
directory is provided for users to build HDF5 library and
tools from command line.
- hdf55build takes the following options:
- /vs8 Build HDF5 using Visual Studio 2005
+ hdf5build takes the following options:
/vs9 Build HDF5 using Visual Studio 2008
- Note: Default is Visual Studio 2005
/fort Build HDF5 with Fortran libraries
/ivf101 Build HDF5 Fortran using Intel Visual Fortran 10.1
- Note: Default is Intel Visual Fortran 9.1
+ /ivf111 Build HDF5 Fortran using Intel Visual Fortran 11.1
+ /nodebug Build HDF5 release versions only
/useenv Build HDF5 using compiler settings defined
in the environment, rather than the IDE.
/? Help information
@@ -148,6 +143,9 @@ notes in INSTALL_Windows.txt before starting below procedures.
tools. To use this option, HDF5
Fortran libraries must have been built.
+ nodebug option can be added to any of the above options to only
+ test the release versions.
+
Invoke a command prompt window and run hdf5check with appropriate
option. Users are encouraged to pipe the test output into a file.
You should find no "*FAILED*" marks.