diff options
author | Allen Byrne <byrn@hdfgroup.org> | 2010-05-12 18:51:33 (GMT) |
---|---|---|
committer | Allen Byrne <byrn@hdfgroup.org> | 2010-05-12 18:51:33 (GMT) |
commit | 84103cef854a758a8d5dcd270ba36e2495ed3282 (patch) | |
tree | f11548eec782a94edda60d2f78edb7f320d8b4c2 /release_docs/INSTALL_Windows_From_Command_Line.txt | |
parent | 08ce72aebd7b8957a11c365f95b4bbded708e91f (diff) | |
download | hdf5-84103cef854a758a8d5dcd270ba36e2495ed3282.zip hdf5-84103cef854a758a8d5dcd270ba36e2495ed3282.tar.gz hdf5-84103cef854a758a8d5dcd270ba36e2495ed3282.tar.bz2 |
[svn-r18773] Add files to support building library with CMake
Tested: Local linux
Diffstat (limited to 'release_docs/INSTALL_Windows_From_Command_Line.txt')
-rwxr-xr-x | release_docs/INSTALL_Windows_From_Command_Line.txt | 28 |
1 files changed, 15 insertions, 13 deletions
diff --git a/release_docs/INSTALL_Windows_From_Command_Line.txt b/release_docs/INSTALL_Windows_From_Command_Line.txt index ede2133..19f7be5 100755 --- a/release_docs/INSTALL_Windows_From_Command_Line.txt +++ b/release_docs/INSTALL_Windows_From_Command_Line.txt @@ -5,12 +5,15 @@ 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 .NET 2003 or Visual Studio VS2005 or Intel Fortran 91. 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. + + 2. Building and testing HDF5 C/C++/Fortran libraries and utilities using + CMake tools. Refer to CMAKE_Windows.txt file for detailed information. For all other Windows development tools, HDF5 should be built in the development environment. Please refer to INSTALL_Windows.txt @@ -37,14 +40,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\ + C:\Program Files\Microsoft Visual Studio 9\Common7\Tools\ - If you are using Visual Studio 2008, use "vs90comntools" - 1.2 Run batch file copy_hdf.bat. Go to c:\MyHDFstuff\hdf5\windows and run copy_hdf.bat. @@ -81,12 +82,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 - /ivf91 Build HDF5 Fortran using Intel Visual Fortran 9.1 /ivf101 Build HDF5 Fortran using Intel Visual Fortran 10.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 +109,13 @@ 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 - /ivf91 Build HDF5 Fortran using Intel Visual Fortran 9.1 /ivf101 Build HDF5 Fortran using Intel Visual Fortran 10.1 + /ivf111 Build HDF5 Fortran using Intel Visual Fortran 11.1 + /nodebug Build HDF5 release versions only + Note: Default is to build debug and release versions /useenv Build HDF5 using compiler settings defined in the environment, rather than the IDE. /? Help information @@ -148,6 +147,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. |