H4H5tools version 1.0 release in July 2002

1. Introduction

This document describes the h4h5tools and contains information on the platforms tested and limitations. 
H4h5tools include three products, H4toH5 conversion library, H4toH5 conversion utility and H5toH4 conversion
utility.

Both H4toH5 conversion library and H4toH5 conversion utility follow HDF4 to HDF5 mapping document.
This document can be found at:
http://hdf.ncsa.uiuc.edu/HDF5/doc/ADGuide/H4toH5Mapping.pdf

The H4toH5 conversion library user's guide and reference manual can be found at:
http://hdf.ncsa.uiuc.edu/h4toh5/h4toh5lib_UG.pdf
http://hdf.ncsa.uiuc.edu/h4toh5/h4toh5lib_RM.pdf

If you have any questions or comments, please send them to:
hdfhelp@ncsa.uiuc.edu


2. Platforms Tested
H4H5tools have been tested on all the platforms that HDF4 and HDF5 support. Please check
http://hdf.ncsa.uiuc.edu/HDF5/release/platforms5.html. 

3. Prerequisites

1) HDF (version 4.1r5) and supported libraries 
2) HDF5 (version 1.4.4) library
3) The absolute path of HDF5 library is in LD_LIBRARY_PATH

4. Install  

Unix install: see install.txt
Windows 2000 install: see install_windows.txt

5. Limitations

1) In this release, all HDF5 property list parameters are set as H5P_DEFAULT. 

2) On windows 2000 platform, 
   a) We are only providing h4toh5 library based on two combinations of HDF4 and HDF5 in the binary release.
     Static library: use only HDF4 and HDF5 release version of static libraries.
     DLL: use debug version of HDF4 DLL and release version of HDF5 DLL.
     When an application wants to use H4toh5 DLL, it must connect with **DEBUG** DLLs of HDF4 libraries for
     both release and debug mode of the application. 
     The image routines will fail when using other combinations of HDF4 and HDF5 DLL libraries to build the H4toh5 library.
   b) We provide the project file on how to build h4toh5 library based on other combinations of HDF4 and HDF5 in the 
      source release. Users who want to use these two libraries are warned that it may be failed.

6. Known problems

* On IA64 systems one has to use -DIA64 compilation flag to compile
  h4h5tools. After configuration step manually modify
  Makefile in the lib/src,lib/test, utils/h4toh5 and utils/h5toh4 
  directories to add -DIA64 to the compilation flags.

	* On IA32 and IA64 systems, if you use a compiler other than GCC (such as
	  Intel's ecc or icc compilers), you will need to modify the generated
	  "libtool" program after configuration is finished. On or around line 104
	  of the libtool file, there are lines which look like:

          # How to pass a linker flag through the compiler.
          wl=""

      change these lines to this:

          # How to pass a linker flag through the compiler.
          wl="-Wl,"














