diff options
Diffstat (limited to 'release_docs')
| -rw-r--r-- | release_docs/INSTALL_Windows.txt | 334 |
1 files changed, 21 insertions, 313 deletions
diff --git a/release_docs/INSTALL_Windows.txt b/release_docs/INSTALL_Windows.txt index aeee2eb..61487fd 100644 --- a/release_docs/INSTALL_Windows.txt +++ b/release_docs/INSTALL_Windows.txt @@ -2,7 +2,7 @@ HDF5 Build and Install Instructions for Windows 2000/NT/98. ---------------------------------------------------------- The instructions which follow assume that you will be using the -source code release 'zip' file (hdf5-1_4_0.zip). +source code release 'zip' file (hdf5-1_4_3.zip). ***************************WARNINGS**************************** Please read CAREFULLY about Preconditions before you go to the @@ -19,7 +19,7 @@ Preconditions c:\ (any drive) MyHDFstuff\ (any folder name) - 3. Run WinZip on hdf5-1_4_0.zip (the entire source tree) and + 3. Run WinZip on hdf5-1_4_3.zip (the entire source tree) and extract hdf5 package into c:\MyHDFstuff(or whatever drive and folder name you would like to choose). This creates a directory called 'hdf5xxx'under MyHDFstuff which contains @@ -30,14 +30,6 @@ Preconditions with hdf5 lib. If you have your own version read section VI about the zlib library. - 5. You do need hdf4 (hdf and mfhdf) static and dll libraries - to generate hdf4-related tools. - - 6. Currently you can build and test either hdf5 libraries - and non-hdf4 related tools or hdf5 libraries and hdf4 - related tools;but not BOTH.In other words,you may either - follow Section II or Section III but NOT both Sections to - build HDF5 libraries and related tools. --------------------------------------------------------------- @@ -46,12 +38,11 @@ The following sections discuss installation procedures in detail: Section I: What do we build and install Section II: Building and testing hdf5 libraries and non-hdf4 related hdf5 tools - Section III: Building and testing hdf5 libraries and all hdf5 tools - Section IV: Building an application using the HDF5 library or + Section III: Building an application using the HDF5 library or DLL - Section V: Some more helpful pointers - Section VI: ZLIB library - removing or changing the path + Section IV: Some more helpful pointers + Section V: ZLIB library - removing or changing the path *************************************************************** @@ -73,7 +64,10 @@ What do we build and install? debug and release version HDF5 tools: - non-hdf4 related tools and hdf4 related tools + non-hdf4 related tools + for hdf4 related tools, please check http://hdf.ncsa.uiuc.edu/h4toh5/ + and ftp://hdf.ncsa.uiuc.edu/HDF5/h4toh5/ + HDF5 library testing programs: hdf5 library related comprehensive tests @@ -122,15 +116,7 @@ STEP 1: Building hdf5 libraries and non-hdf4 related tools and tests. - NOTE : "all" is a dummy target. You will get a link - error when "all.exe." is built: - - LINK: error LNK2001: unresolved external symbol - _mainCRTStartup..... - all.exe - 2 error(s), .... - - Warning messages can be ignored. The "all.exe" is never - created, so it is OK. + Warning messages can be ignored. When the debug or release build is done the directories listed below will contain the following files: @@ -217,7 +203,7 @@ STEP 1: Building hdf5 libraries and non-hdf4 related tools where non-hdf4 related tools directory is one of the following: - h5dump(dll) + h5dump(dll) h5ls(dll) @@ -226,6 +212,8 @@ STEP 1: Building hdf5 libraries and non-hdf4 related tools h5import(dll) h5repart(dll) + + gifconv(dll) Test and tool directory contains debug and release @@ -411,290 +399,7 @@ STEP 3: BUILDING THE EXAMPLES should be executed before chunkread.exe and readtest.exe due to dependencies among these files. -************************************************************** - -Section III: BUILDING AND TESTING HDF5 LIBRARIES AND ALL HDF5 TOOLS - -------------------WARNINGS--------------------------------- - -1. This section is specifically for building HDF5 tools that needs to call HDF4 library. - -Currently we are supporting two hdf4-relatedtools: H4toh5 converter -and H5toh4 converter. If you are not using these tools, please go -back to Section II for building and installing information. - -2. This section builds and tests all versions of hdf5 libraries, -testing programs and tools covered in section II. -Additionally, it also builds and tests hdf4-related tools. We may refer some duplicated parts of this section to section II. - -3. In case - a) you don't install hdf libraries and related tools in - your machine, - b) or if the top directory of your hdf4 libraries and - tools are not under C:\hdf41r4 and you are not familar - on how to change settings of VC++ projects. - - you may get binary distribution from -ftp://ftp.ncsa.uiuc.edu/HDF/HDF/HDF4.1r4/windows_precompiled_code/HDF41r4.zip -and use Winzip to unpack HDF41r4.zip into C:\hdf41r4. - -4. We assume that you've installed hdf4(mfhdf and hdf) -libraries into drive C. The top level path should be -C:\HDF41r4. Under C:\HDF41r4 it should at least -include the following six directories: - -C:\HDF41r4\bin where hdf4 utilities are stored - -C:\HDF41r4\dlllib where release dll versions of hdf and mfhdf -libraries and export libraries of dlls are stored - -C:\HDF41r4\dlllibdbg where debug dll versions of hdf and mfhdf -libraries and export libraries of dlls are stored - -C:\HDF41r4\lib where release versions of hdf and mfhdf -libraries are stored - -C:\HDF41r4\libdbg where debug versions of hdf and mfhdf -libraries are stored - -C:\HDF41r4\include where header files are included - -Make sure that you copy all *.dll files under C:\HDF41r4 into Windows -system directory before the next step. - -If your path of hdf libraries and mfhdf libraries is different -from the default assumption, please DO follow No.4 of Step 1 on -the following: - - -Step 1. - - 1. Unpack all_withhdf4.zip in 'hdf5' and move the zlib.dll - from c:\myHDFstuff\hdf5\src\zlib\dll to the Windows - system directory. - - The system directory can usually be found under the path - C:\WINNT\system or C:\WIN98\system - - 2. Invoke Microsoft Visual C++, go to "File" and select the - "Open Workspace" option. - - Then open the c:\myHDFstuff\hdf5\proj\all\all.dsw - workspace. - - 3. This part is for users who are familar with handling - settings of VC++ project and store their hdf4 libraries - not under C:\hdf41r4. Other users can skip this part. - - 3.1 Change the path where hdf4 library header files are - located - - a) On the View menu, click Workspace, you may see a - pop-up window with names of projects in all.dsw. - b) click FileView on the bottom of this window if you - are not seeing "all files big files ......." - c) You need to modify settings of four projects: h4toh5, - h4toh5dll,h5toh4 and h5toh4dll. - You also need to modify both debug and release - versions. - - You may do as follows: - c1)Right click the selected project and then click - "Settings" - c2)A dialog box called "Project Settings" will be - poped up - c3)On the upper-left part of the "Project Settings" - box, you may find a small window "Settings for". - Make sure inside this "Settings for" box is either - "Win32 Debug" or "Win32 Release". Change contents - into "Win32 Debug" or "Win32 Release" otherwise. - Remember the version(Win32 Release or Debug) you - chose. - c4)On the upper-right menu of the "Project Settings" - window, find C/C++ and click it. - c5)Just below the upper-right menu, find a small - window called category, make sure that - "Preprocessor" appear in this window. - c6)In the middle of "Project Settings" windows, you - may find a box called - "Additional include directories:" . You may notice - "C:\hdf41r4\include" inside this box. This is the - path where the default hdf4 header files is - included. Replace only this path - (C:\hdf41r4\include) with your own path that - includes your hdf4 header files. Don't touch any - other paths. - c7)After you've done this, click OK at the bottom of - "Project Settings" window. - c8)Repeat c1)-c7)but change contents of "settings - for" in c3) from "Win32 Release" to "Win32 Debug" - or vice versa. - d) repeat step c) for the other three projects. - - 3.2 Replace the user's hdf and mfhdf libraries, export - libraries of hdf and mfhdf DLLs - - You also need to modify four projects: h4toh5, - h4toh5dll, h5toh4 and h5toh4dll: - a) select project h4toh5 following instruction 4.1 a) - and b). - b) click h4toh5, you may find four libraries: - hm414d.lib,hd414d.lib and hm414.lib,hd414.lib - attached under the project h4toh5. hm414d.lib and - hd414d.lib are debug versions of mfhdf and hdf - libraries. hm414.lib and hd414.lib are release - versions of mfhdf and hdf libraries. - c) select these four libraries; go back to Edit menu and - choose "delete" option to delete template of these - libraries. - d) select project h4toh5 and right click the mouse, find - "Add Files to Projects", follow the instructions on - the pop-up box, to insert your own hm414d.lib, - hd414d.lib,hm414.lib and hd414.lib. You must know - their paths at first. - e) select project h4toh5dll following instruction 4.1 a) - and b). - f) click h4toh5dll, you may also find four libraries: - hd414m.lib,hd414md.lib and hm414m.lib,hd414m.lib - attached under the project h4toh5dll. These libraries - are debug and release versions of Export libraries of - mfhdf and hdf DLLs. - g) select these four libraries; go back to Edit menu and - choose "delete" option to delete template of these - libraries. - h) select project h4toh5dll and right click the mouse, - find "Add Files to Projects", follow the instructions - on the pop-up box, to insert your own hd414m.lib, - hd414md.lib,hm414m.lib and hd414m.lib. You must know - their paths at first. - i) repeat a)-h) for h5toh4 and h5toh4dll. - - 4. Select "Build", then Select "Set Active Configuration". - - On Windows platform select as the active configuration - - "all -- Win32 Debug" to build debug versions - single-threaded static libraries, - and tests. - or - - "all -- Win32 Release" to build release versions of - single-threaded static - libraries, and tests. - - - NOTE : "all" is a dummy target. You will get a link - error when "all.exe." is built: - - LINK: error LNK2001: unresolved external symbol - _mainCRTStartup..... - all.exe - 2 error(s), .... - - Warning messages can be ignored. The "all.exe" is never - created, so it is OK. - - You should see hdf5 libraries, tests and tools under - section II Step 1. - In addtion, under c:\MyHDFstuff\hdf5\tools\ - - You may also find: - h4toh5 - h5toh4 - h4toh5dll - h5toh4dll - for both the debug and release versions. - -STEP 2: testing hdf5 libraries and all hdf5 tools - - 1. hdf5 library testing - Follow all instructions of the same part in Section II - STEP 2 - - 2. non-hdf4 related tools testing - Follow all instructions of the same part in Section II - STEP 2 - - 3. hdf4-related tools testing - - 1) h4toh5 converter tool testing - - First cd into hdf5\tools - - Go to a) b) c) or d) to test your chosen version - - a) release static version - type: - h4toh5testrun release >"Your output filename" - - b) release dll version - type: - h4toh5testrun release dll > "Your output filename" - - c) debug static version - type: - h4toh5testrun debug >"Your output filename" - - d) debug dll version - type: - h4toh5testrun debug dll >"Your output filename" - - We are using "fc" command to compare whether h4toh5 - converter converts the hdf4 file into the correct hdf5 - file.In your output files, Please only pay attention to - those lines which start with - "FC:",you should find "FC: no differences encountered" - for all tested hdf4 files in your output. - - 2) h5toh4 converter tool testing - - To test the h5toh4 utility, you need to have hdf4 - dumper utility "hdp" in your system. - - Note: Currently h5toh4 release dll doesn't work - for all test cases possibly due to windows dealing - with "free memory" conventions for dll versions. - - 1) If your hdp utility is located at C:\hdf41r4\bin, - you may skip this part. Otherwise, copy your hdp.exe - file into the directory where your hdf5 tools are - located. For example, if your hdf5 tools directory is - C:\myHDFstuff\hdf5\tools; please copy hdp.exe into - this directory. - - 2) cd into \...\hdf5\tools. - Go to a) b) c) or d) to test your chosen version - - a) release static version - type: - h5toh4testrun release >"Your output filename" - - b) release dll version - type: - h5toh4testrun release dll > "Your output filename" - - c) debug static version - type: - h5toh4testrun debug >"Your output filename" - - d) debug dll version - type: - h5toh4testrun debug dll >"Your output filename" - - We are using "fc" command to compare whether h5toh4 - converter converts the hdf5 file into the correct hdf4 - file.In your output files, Please only pay attention to - those lines which start with - "FC:",you should find "FC: no differences encountered" - for all tested hdf4 files in your output. - Warnings appear on the prompt when testing h5toh4 converter - can be ignored. - - -STEP 3: BUILDING THE EXAMPLES - - Follow all instructions of SECTION II STEP 3. - -Section IV: +Section III: BUILDING AN APPLICATION USING THE HDF5 LIBRARY OR DLL- SOME HELPFUL POINTERS ==================================================================== @@ -765,7 +470,7 @@ To use the DLL: e) The directories listed in the PATH environment variable. -Section V: +Section IV: MORE HELPFUL POINTERS ===================== @@ -828,7 +533,7 @@ DLL... hints: -Section VI: +Section V: ZLIB LIBRARY- REMOVING OR CHANGING THE PATH ============================================ @@ -842,8 +547,8 @@ Removing the zlib library completely: delete(press the 'delete' key) it. Next open the H5config.h and H5pubconf.h files from the src directory. Remove the the following two lines: - #define HAVE_LIBZ 1 - #define HAVE_COMPRESS2 + #define H5_HAVE_LIBZ 1 + #define H5_HAVE_COMPRESS2 then save the file. @@ -864,3 +569,6 @@ Replacing the zlib library: hdf5dll project. You may also want to replace the zlib.h and zconf.h files which are in the src directory with your own versions of these files. Then recompile the all project. + +Please send email to hdfhelp@ncsa.uiuc.edu for further assistance. + |