[DebianGIS-dev] r831 - in packages/libhdf4/branches/upstream/current: . bin config hdf hdf/fmpool hdf/src hdf/src/fort_ps hdf/test hdf/test/fort_ps hdf/util hdf/util/testfiles hdf/util/testfiles/fp2hdf man mfhdf mfhdf/c++ mfhdf/dumper mfhdf/dumper/testfiles mfhdf/fortran mfhdf/fortran/config mfhdf/fortran/fort_ps mfhdf/fortran/msoft mfhdf/fortran/vms mfhdf/hdfimport mfhdf/hdiff mfhdf/hdiff/testfiles mfhdf/hrepack mfhdf/libsrc mfhdf/libsrc/config mfhdf/ncdump mfhdf/ncgen mfhdf/nctest mfhdf/port mfhdf/xdr release_notes
frankie at alioth.debian.org
frankie at alioth.debian.org
Tue May 15 09:53:08 UTC 2007
Author: frankie
Date: 2007-05-15 09:53:05 +0000 (Tue, 15 May 2007)
New Revision: 831
Added:
packages/libhdf4/branches/upstream/current/INSTALL_WINDOWS.txt
packages/libhdf4/branches/upstream/current/MANIFEST
packages/libhdf4/branches/upstream/current/Makefile.am
packages/libhdf4/branches/upstream/current/aclocal.m4
packages/libhdf4/branches/upstream/current/bin/
packages/libhdf4/branches/upstream/current/bin/chkmanifest
packages/libhdf4/branches/upstream/current/bin/compile
packages/libhdf4/branches/upstream/current/bin/config.guess
packages/libhdf4/branches/upstream/current/bin/config.sub
packages/libhdf4/branches/upstream/current/bin/depcomp
packages/libhdf4/branches/upstream/current/bin/install-sh
packages/libhdf4/branches/upstream/current/bin/locate_sw
packages/libhdf4/branches/upstream/current/bin/missing
packages/libhdf4/branches/upstream/current/bin/mkinstalldirs
packages/libhdf4/branches/upstream/current/bin/regenerate.sh
packages/libhdf4/branches/upstream/current/bin/runtest
packages/libhdf4/branches/upstream/current/bin/snapshot
packages/libhdf4/branches/upstream/current/config/BlankForm
packages/libhdf4/branches/upstream/current/config/freebsd
packages/libhdf4/branches/upstream/current/config/hpux11.00
packages/libhdf4/branches/upstream/current/config/ia64-linux-gnu
packages/libhdf4/branches/upstream/current/config/irix6.x
packages/libhdf4/branches/upstream/current/config/linux-gnu
packages/libhdf4/branches/upstream/current/config/osf5.x
packages/libhdf4/branches/upstream/current/config/powerpc-apple
packages/libhdf4/branches/upstream/current/config/powerpc-ibm-aix5.x
packages/libhdf4/branches/upstream/current/config/solaris2.x
packages/libhdf4/branches/upstream/current/config/sv1-cray
packages/libhdf4/branches/upstream/current/config/unicos10.0.X
packages/libhdf4/branches/upstream/current/config/unicosmk2.0.6.X
packages/libhdf4/branches/upstream/current/configure.ac
packages/libhdf4/branches/upstream/current/hdf/COPYING
packages/libhdf4/branches/upstream/current/hdf/COPYRIGHT
packages/libhdf4/branches/upstream/current/hdf/Makefile.am
packages/libhdf4/branches/upstream/current/hdf/README.33r4
packages/libhdf4/branches/upstream/current/hdf/src/INSTALL
packages/libhdf4/branches/upstream/current/hdf/src/Makefile.am
packages/libhdf4/branches/upstream/current/hdf/src/cszip.c
packages/libhdf4/branches/upstream/current/hdf/src/cszip.h
packages/libhdf4/branches/upstream/current/hdf/src/h4config.h.in
packages/libhdf4/branches/upstream/current/hdf/test/MAKECOM.OLD
packages/libhdf4/branches/upstream/current/hdf/test/Makefile.am
packages/libhdf4/branches/upstream/current/hdf/test/tdupimgs.c
packages/libhdf4/branches/upstream/current/hdf/test/tszip.c
packages/libhdf4/branches/upstream/current/hdf/util/Makefile.am
packages/libhdf4/branches/upstream/current/hdf/util/README.fp2hdf
packages/libhdf4/branches/upstream/current/hdf/util/README.fp2hdf.test
packages/libhdf4/branches/upstream/current/hdf/util/fp2hdf.test
packages/libhdf4/branches/upstream/current/hdf/util/h4cc.in
packages/libhdf4/branches/upstream/current/hdf/util/h4fc.in
packages/libhdf4/branches/upstream/current/hdf/util/h4redeploy.in
packages/libhdf4/branches/upstream/current/hdf/util/testfiles/fp2hdf/
packages/libhdf4/branches/upstream/current/hdf/util/testfiles/fp2hdf/h100x100
packages/libhdf4/branches/upstream/current/hdf/util/testfiles/fp2hdf/h100x100h
packages/libhdf4/branches/upstream/current/hdf/util/testfiles/fp2hdf/h100x100hv
packages/libhdf4/branches/upstream/current/hdf/util/testfiles/fp2hdf/h60x75
packages/libhdf4/branches/upstream/current/hdf/util/testfiles/fp2hdf/h60x75n
packages/libhdf4/branches/upstream/current/hdf/util/testfiles/fp2hdf/h60x75v
packages/libhdf4/branches/upstream/current/hdf/util/testfiles/fp2hdf/pal.hdf
packages/libhdf4/branches/upstream/current/hdf/util/testfiles/fp2hdf/t100x100
packages/libhdf4/branches/upstream/current/hdf/util/testfiles/head.r24.gz
packages/libhdf4/branches/upstream/current/hdf/util/testfiles/head.r8.gz
packages/libhdf4/branches/upstream/current/hdf/util/testutil.sh.in
packages/libhdf4/branches/upstream/current/man/Makefile.am
packages/libhdf4/branches/upstream/current/mfhdf/Makefile.am
packages/libhdf4/branches/upstream/current/mfhdf/README.HDF.33
packages/libhdf4/branches/upstream/current/mfhdf/dumper/Makefile.am
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/Example6.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/Image_with_Palette.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/LongDataset.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/ctxtr2r.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/dumpgr-19.out
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/dumpsds-10.out
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/dumpsds-11.out
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/grtdfi322.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/grtdfui162.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/grtdfui82.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/grtdfui83.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/grtdfui84.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/star.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/swf32.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/swf32_fileattr.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/swi16.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/swi8.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/tdata.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/tdf24.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/tdfr8f.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/test.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/tvattr.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/tvset.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testhdp.sh.in
packages/libhdf4/branches/upstream/current/mfhdf/fortran/Makefile.am
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-apple.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-solaris64.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-apple.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-solaris64.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/netcdf-apple.inc
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/netcdf-solaris64.inc
packages/libhdf4/branches/upstream/current/mfhdf/fortran/test_nc.cdl
packages/libhdf4/branches/upstream/current/mfhdf/fortran/test_nc.nc
packages/libhdf4/branches/upstream/current/mfhdf/hdfimport/
packages/libhdf4/branches/upstream/current/mfhdf/hdfimport/Makefile.am
packages/libhdf4/branches/upstream/current/mfhdf/hdfimport/Makefile.in
packages/libhdf4/branches/upstream/current/mfhdf/hdfimport/hdfimport.c
packages/libhdf4/branches/upstream/current/mfhdf/hdfimport/hdfimport.input1
packages/libhdf4/branches/upstream/current/mfhdf/hdfimport/hdfimport.out1
packages/libhdf4/branches/upstream/current/mfhdf/hdfimport/hdfimport.out2
packages/libhdf4/branches/upstream/current/mfhdf/hdfimport/hdfimporttest.c
packages/libhdf4/branches/upstream/current/mfhdf/hdfimport/testutil.sh.in
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/Makefile.am
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/Makefile.in
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/hdiff.c
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/hdiff.h
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/hdiff_array.c
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/hdiff_gattr.c
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/hdiff_gr.c
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/hdiff_list.c
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/hdiff_list.h
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/hdiff_main.c
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/hdiff_mattbl.c
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/hdiff_mattbl.h
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/hdiff_misc.c
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/hdiff_sds.c
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/hdiff_table.c
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/hdiff_table.h
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/hdiff_vs.c
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/hdifftst.c
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/testfiles/
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/testfiles/hdiff_01.txt
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/testfiles/hdiff_02.txt
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/testfiles/hdiff_03.txt
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/testfiles/hdiff_04.txt
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/testfiles/hdiff_05.txt
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/testfiles/hdiff_06.txt
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/testfiles/hdiff_07.txt
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/testfiles/hdiff_08.txt
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/testfiles/hdiff_09.txt
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/testfiles/hdiff_10.txt
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/testfiles/hdiff_11.txt
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/testfiles/hdifftst1.hdf
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/testfiles/hdifftst2.hdf
packages/libhdf4/branches/upstream/current/mfhdf/hdiff/testhdiff.sh
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/Makefile.am
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/Makefile.in
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack.h
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_all.sh
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_an.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_an.h
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_check.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_cmp.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_gr.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_gr.h
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_list.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_lsttable.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_lsttable.h
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_main.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_opttable.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_opttable.h
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_pal.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_pal.h
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_parse.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_parse.h
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_sds.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_sds.h
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_sdutil.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_sdutil.h
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_utils.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_utils.h
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_vg.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_vg.h
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_vs.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/hrepack_vs.h
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/image24pixel.txt
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/image24plane.txt
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/image8.txt
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/info.txt
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/pal_rgb.h
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/test_hrepack.sh
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/test_hrepack_add.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/test_hrepack_add.h
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/test_hrepack_main.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/test_hrepack_verify.c
packages/libhdf4/branches/upstream/current/mfhdf/hrepack/test_hrepack_verify.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/Makefile.am
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-apple.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-solaris64.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/hdftest.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/temptySDSs.c
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/tidtypes.c
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/trank0.c
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/tsd.c
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/tszip.c
packages/libhdf4/branches/upstream/current/mfhdf/ncdump/Makefile.am
packages/libhdf4/branches/upstream/current/mfhdf/ncgen/Makefile.am
packages/libhdf4/branches/upstream/current/mfhdf/nctest/Makefile.am
packages/libhdf4/branches/upstream/current/mfhdf/nctest/test_unlim.cdl
packages/libhdf4/branches/upstream/current/mfhdf/nctest/test_unlim.nc
packages/libhdf4/branches/upstream/current/mfhdf/nctest/varget_unlim.c
packages/libhdf4/branches/upstream/current/mfhdf/port/Makefile.am
packages/libhdf4/branches/upstream/current/mfhdf/xdr/Makefile.am
packages/libhdf4/branches/upstream/current/release_notes/HISTORY.txt
packages/libhdf4/branches/upstream/current/release_notes/RELEASE.txt
packages/libhdf4/branches/upstream/current/release_notes/misc_docs.txt
Removed:
packages/libhdf4/branches/upstream/current/config.guess
packages/libhdf4/branches/upstream/current/config.sub
packages/libhdf4/branches/upstream/current/config/mh-aix
packages/libhdf4/branches/upstream/current/config/mh-alpha
packages/libhdf4/branches/upstream/current/config/mh-decstation
packages/libhdf4/branches/upstream/current/config/mh-fbsd
packages/libhdf4/branches/upstream/current/config/mh-fujivp
packages/libhdf4/branches/upstream/current/config/mh-hpux
packages/libhdf4/branches/upstream/current/config/mh-hpux11
packages/libhdf4/branches/upstream/current/config/mh-ia64
packages/libhdf4/branches/upstream/current/config/mh-irix32
packages/libhdf4/branches/upstream/current/config/mh-irix5
packages/libhdf4/branches/upstream/current/config/mh-irix6
packages/libhdf4/branches/upstream/current/config/mh-linux
packages/libhdf4/branches/upstream/current/config/mh-mac
packages/libhdf4/branches/upstream/current/config/mh-solaris
packages/libhdf4/branches/upstream/current/config/mh-solarisx86
packages/libhdf4/branches/upstream/current/config/mh-sun
packages/libhdf4/branches/upstream/current/config/mh-t3e
packages/libhdf4/branches/upstream/current/config/mh-unicos
packages/libhdf4/branches/upstream/current/configure.in
packages/libhdf4/branches/upstream/current/hdf/MAKE.COM
packages/libhdf4/branches/upstream/current/hdf/build.inc
packages/libhdf4/branches/upstream/current/hdf/jpeg/
packages/libhdf4/branches/upstream/current/hdf/pablo/
packages/libhdf4/branches/upstream/current/hdf/util/testfiles/head.r24.Z
packages/libhdf4/branches/upstream/current/hdf/util/testfiles/head.r8.Z
packages/libhdf4/branches/upstream/current/hdf/util/testutil.sh
packages/libhdf4/branches/upstream/current/hdf/zlib/
packages/libhdf4/branches/upstream/current/install-sh
packages/libhdf4/branches/upstream/current/mfhdf/Makefile.in_orig
packages/libhdf4/branches/upstream/current/mfhdf/aclocal.m4
packages/libhdf4/branches/upstream/current/mfhdf/configure
packages/libhdf4/branches/upstream/current/mfhdf/configure.in
packages/libhdf4/branches/upstream/current/mfhdf/doc/
packages/libhdf4/branches/upstream/current/mfhdf/dumper/Example6.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/Image_with_Palette.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/LongDataset.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/Makefile.in_orig
packages/libhdf4/branches/upstream/current/mfhdf/dumper/ctxtr2r.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/depend
packages/libhdf4/branches/upstream/current/mfhdf/dumper/grtdfi322.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/grtdfui162.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/grtdfui82.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/grtdfui83.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/grtdfui84.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/star.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/swf32.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/swf32_fileattr.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/swi16.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/swi8.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/tdata.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/tdf24.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/tdfr8f.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/test.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testhdp.sh
packages/libhdf4/branches/upstream/current/mfhdf/dumper/tvattr.hdf
packages/libhdf4/branches/upstream/current/mfhdf/dumper/tvset.hdf
packages/libhdf4/branches/upstream/current/mfhdf/fortran/Makefile.in_orig
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/Makefile.in_orig
packages/libhdf4/branches/upstream/current/mfhdf/ncdump/Makefile.in_orig
packages/libhdf4/branches/upstream/current/mfhdf/ncgen/Makefile.in_orig
packages/libhdf4/branches/upstream/current/mfhdf/nctest/Makefile.in_orig
packages/libhdf4/branches/upstream/current/mfhdf/pablo/
packages/libhdf4/branches/upstream/current/mfhdf/port/Makefile.in_orig
packages/libhdf4/branches/upstream/current/mfhdf/xdr/Makefile.in_orig
packages/libhdf4/branches/upstream/current/mkinstalldirs
packages/libhdf4/branches/upstream/current/release_notes/ABOUT_4.1r4
packages/libhdf4/branches/upstream/current/release_notes/compile.txt
Modified:
packages/libhdf4/branches/upstream/current/COPYING
packages/libhdf4/branches/upstream/current/INSTALL
packages/libhdf4/branches/upstream/current/Makefile.in
packages/libhdf4/branches/upstream/current/README
packages/libhdf4/branches/upstream/current/Win32.nofortran.zip
packages/libhdf4/branches/upstream/current/Win32.zip
packages/libhdf4/branches/upstream/current/configure
packages/libhdf4/branches/upstream/current/hdf/Makefile.in
packages/libhdf4/branches/upstream/current/hdf/fmpool/Makefile.in
packages/libhdf4/branches/upstream/current/hdf/src/Makefile.in
packages/libhdf4/branches/upstream/current/hdf/src/atom.c
packages/libhdf4/branches/upstream/current/hdf/src/df24.c
packages/libhdf4/branches/upstream/current/hdf/src/dfan.c
packages/libhdf4/branches/upstream/current/hdf/src/dfan.h
packages/libhdf4/branches/upstream/current/hdf/src/dffunc.inc
packages/libhdf4/branches/upstream/current/hdf/src/dfp.c
packages/libhdf4/branches/upstream/current/hdf/src/dfr8.c
packages/libhdf4/branches/upstream/current/hdf/src/dfsd.c
packages/libhdf4/branches/upstream/current/hdf/src/dynarray.c
packages/libhdf4/branches/upstream/current/hdf/src/fort_ps/herrpf.c
packages/libhdf4/branches/upstream/current/hdf/src/fort_ps/herrpff.f
packages/libhdf4/branches/upstream/current/hdf/src/fort_ps/hfilepf.c
packages/libhdf4/branches/upstream/current/hdf/src/fort_ps/hfilepff.f
packages/libhdf4/branches/upstream/current/hdf/src/fort_ps/hprotop.h
packages/libhdf4/branches/upstream/current/hdf/src/fort_ps/mfgrpf.c
packages/libhdf4/branches/upstream/current/hdf/src/fort_ps/mfgrpff.f
packages/libhdf4/branches/upstream/current/hdf/src/fort_ps/vgpf.c
packages/libhdf4/branches/upstream/current/hdf/src/fort_ps/vgpff.f
packages/libhdf4/branches/upstream/current/hdf/src/hbitio.c
packages/libhdf4/branches/upstream/current/hdf/src/hblocks.c
packages/libhdf4/branches/upstream/current/hdf/src/hbuffer.c
packages/libhdf4/branches/upstream/current/hdf/src/hchunks.c
packages/libhdf4/branches/upstream/current/hdf/src/hchunks.h
packages/libhdf4/branches/upstream/current/hdf/src/hcomp.c
packages/libhdf4/branches/upstream/current/hdf/src/hcomp.h
packages/libhdf4/branches/upstream/current/hdf/src/hcompi.h
packages/libhdf4/branches/upstream/current/hdf/src/hcompri.c
packages/libhdf4/branches/upstream/current/hdf/src/hconv.h
packages/libhdf4/branches/upstream/current/hdf/src/hdf.h
packages/libhdf4/branches/upstream/current/hdf/src/hdfi.h
packages/libhdf4/branches/upstream/current/hdf/src/herr.c
packages/libhdf4/branches/upstream/current/hdf/src/herr.h
packages/libhdf4/branches/upstream/current/hdf/src/herrf.c
packages/libhdf4/branches/upstream/current/hdf/src/hextelt.c
packages/libhdf4/branches/upstream/current/hdf/src/hfile.c
packages/libhdf4/branches/upstream/current/hdf/src/hfile.h
packages/libhdf4/branches/upstream/current/hdf/src/hfiledd.c
packages/libhdf4/branches/upstream/current/hdf/src/hfileff.f
packages/libhdf4/branches/upstream/current/hdf/src/hlimits.h
packages/libhdf4/branches/upstream/current/hdf/src/hproto.h
packages/libhdf4/branches/upstream/current/hdf/src/linklist.c
packages/libhdf4/branches/upstream/current/hdf/src/mcache.c
packages/libhdf4/branches/upstream/current/hdf/src/mfan.c
packages/libhdf4/branches/upstream/current/hdf/src/mfgr.c
packages/libhdf4/branches/upstream/current/hdf/src/mfgr.h
packages/libhdf4/branches/upstream/current/hdf/src/mfgrf.c
packages/libhdf4/branches/upstream/current/hdf/src/mfgrff.f
packages/libhdf4/branches/upstream/current/hdf/src/src.inc
packages/libhdf4/branches/upstream/current/hdf/src/trace.h
packages/libhdf4/branches/upstream/current/hdf/src/vattr.c
packages/libhdf4/branches/upstream/current/hdf/src/vg.c
packages/libhdf4/branches/upstream/current/hdf/src/vgf.c
packages/libhdf4/branches/upstream/current/hdf/src/vgff.f
packages/libhdf4/branches/upstream/current/hdf/src/vgp.c
packages/libhdf4/branches/upstream/current/hdf/src/vhi.c
packages/libhdf4/branches/upstream/current/hdf/src/vio.c
packages/libhdf4/branches/upstream/current/hdf/src/vrw.c
packages/libhdf4/branches/upstream/current/hdf/src/vsfld.c
packages/libhdf4/branches/upstream/current/hdf/test/Makefile.in
packages/libhdf4/branches/upstream/current/hdf/test/an.c
packages/libhdf4/branches/upstream/current/hdf/test/bitio.c
packages/libhdf4/branches/upstream/current/hdf/test/extelt.c
packages/libhdf4/branches/upstream/current/hdf/test/forsupf.c
packages/libhdf4/branches/upstream/current/hdf/test/forsupff.f
packages/libhdf4/branches/upstream/current/hdf/test/fort_ps/forsupffp.f
packages/libhdf4/branches/upstream/current/hdf/test/fort_ps/fortest.arg
packages/libhdf4/branches/upstream/current/hdf/test/fort_ps/fortestFp.f
packages/libhdf4/branches/upstream/current/hdf/test/fort_ps/manpf.f
packages/libhdf4/branches/upstream/current/hdf/test/fortest.c
packages/libhdf4/branches/upstream/current/hdf/test/fortest.h
packages/libhdf4/branches/upstream/current/hdf/test/fortestF.f
packages/libhdf4/branches/upstream/current/hdf/test/litend.c
packages/libhdf4/branches/upstream/current/hdf/test/manf.f
packages/libhdf4/branches/upstream/current/hdf/test/mgr.c
packages/libhdf4/branches/upstream/current/hdf/test/mgrf.f
packages/libhdf4/branches/upstream/current/hdf/test/nbit.c
packages/libhdf4/branches/upstream/current/hdf/test/t24f.f
packages/libhdf4/branches/upstream/current/hdf/test/testhdf.c
packages/libhdf4/branches/upstream/current/hdf/test/tproto.h
packages/libhdf4/branches/upstream/current/hdf/test/tvattr.c
packages/libhdf4/branches/upstream/current/hdf/test/tvattrf.f
packages/libhdf4/branches/upstream/current/hdf/test/tvset.c
packages/libhdf4/branches/upstream/current/hdf/test/tvsetf.f
packages/libhdf4/branches/upstream/current/hdf/util/Makefile.in
packages/libhdf4/branches/upstream/current/hdf/util/fp2hdf.c
packages/libhdf4/branches/upstream/current/hdf/util/fptest.c
packages/libhdf4/branches/upstream/current/hdf/util/gif2mem.c
packages/libhdf4/branches/upstream/current/hdf/util/hdf2gif.c
packages/libhdf4/branches/upstream/current/hdf/util/hdfcomp.c
packages/libhdf4/branches/upstream/current/hdf/util/hdfpack.c
packages/libhdf4/branches/upstream/current/hdf/util/vshow.c
packages/libhdf4/branches/upstream/current/man/Makefile.in
packages/libhdf4/branches/upstream/current/mfhdf/Makefile.in
packages/libhdf4/branches/upstream/current/mfhdf/c++/ncvalues.cc
packages/libhdf4/branches/upstream/current/mfhdf/c++/ncvalues.hh
packages/libhdf4/branches/upstream/current/mfhdf/c++/netcdf.cc
packages/libhdf4/branches/upstream/current/mfhdf/c++/netcdf.hh
packages/libhdf4/branches/upstream/current/mfhdf/dumper/Makefile.in
packages/libhdf4/branches/upstream/current/mfhdf/dumper/TEST.COM
packages/libhdf4/branches/upstream/current/mfhdf/dumper/hdp.c
packages/libhdf4/branches/upstream/current/mfhdf/dumper/hdp.h
packages/libhdf4/branches/upstream/current/mfhdf/dumper/hdp_dump.c
packages/libhdf4/branches/upstream/current/mfhdf/dumper/hdp_gr.c
packages/libhdf4/branches/upstream/current/mfhdf/dumper/hdp_list.c
packages/libhdf4/branches/upstream/current/mfhdf/dumper/hdp_sds.c
packages/libhdf4/branches/upstream/current/mfhdf/dumper/hdp_vd.c
packages/libhdf4/branches/upstream/current/mfhdf/dumper/hdp_vg.c
packages/libhdf4/branches/upstream/current/mfhdf/dumper/show.c
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/dumpgr-13.out
packages/libhdf4/branches/upstream/current/mfhdf/dumper/testfiles/dumpgr-15.out
packages/libhdf4/branches/upstream/current/mfhdf/fortran/Makefile.in
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-aix.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-alpha.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-convex.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-dec.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-fbsd.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-fujivp.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-hpux.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-ia64.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-irix32.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-irix4.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-irix5.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-irix6.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-linux.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-mac.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-solaris.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-solarisx86.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-sun.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-t3e.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/ftest-unicos.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-aix.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-alpha.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-convex.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-dec.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-fbsd.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-fujivp.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-hpux.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-ia64.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-irix32.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-irix4.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-irix5.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-irix6.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-linux.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-mac.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-solaris.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-solarisx86.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-sun.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-t3e.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/config/jackets-unicos.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/fort_ps/hdftestp.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/fort_ps/mfsdpf.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/fort_ps/mfsdpff.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/hdftest.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/mfsdf.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/mfsdff.f
packages/libhdf4/branches/upstream/current/mfhdf/fortran/msoft/ftest.for
packages/libhdf4/branches/upstream/current/mfhdf/fortran/msoft/jackets.c
packages/libhdf4/branches/upstream/current/mfhdf/fortran/vms/ftest.for
packages/libhdf4/branches/upstream/current/mfhdf/fortran/vms/ftest.m4
packages/libhdf4/branches/upstream/current/mfhdf/fortran/vms/jackets.c
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/Makefile.in
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/array.c
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/cdf.c
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/cdftest.c
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-aix.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-alpha.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-convex.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-dec.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-fbsd.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-fujivp.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-hpux.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-ia64.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-irix32.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-irix4.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-irix5.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-irix6.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-linux.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-mac.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-solaris.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-solarisx86.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-sun.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-t3e.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-unicos.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/config/netcdf-vms.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/hdf2netcdf.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/hdftest.c
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/mfhdf.h
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/mfsd.c
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/netcdf.h.in
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/putget.c
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/var.c
packages/libhdf4/branches/upstream/current/mfhdf/libsrc/xdrposix.c
packages/libhdf4/branches/upstream/current/mfhdf/ncdump/Makefile.in
packages/libhdf4/branches/upstream/current/mfhdf/ncdump/ncdump.c
packages/libhdf4/branches/upstream/current/mfhdf/ncgen/Makefile.in
packages/libhdf4/branches/upstream/current/mfhdf/ncgen/make.com
packages/libhdf4/branches/upstream/current/mfhdf/ncgen/ncgen.l
packages/libhdf4/branches/upstream/current/mfhdf/nctest/Makefile.in
packages/libhdf4/branches/upstream/current/mfhdf/nctest/driver.c
packages/libhdf4/branches/upstream/current/mfhdf/nctest/slabs.c
packages/libhdf4/branches/upstream/current/mfhdf/nctest/tests.h
packages/libhdf4/branches/upstream/current/mfhdf/port/Makefile.in
packages/libhdf4/branches/upstream/current/mfhdf/xdr/Makefile.in
packages/libhdf4/branches/upstream/current/release_notes/bugs_fixed.txt
Log:
[svn-upgrade] Integrating new upstream version, libhdf4 (4.2r1)
Modified: packages/libhdf4/branches/upstream/current/COPYING
===================================================================
--- packages/libhdf4/branches/upstream/current/COPYING 2007-05-15 09:05:29 UTC (rev 830)
+++ packages/libhdf4/branches/upstream/current/COPYING 2007-05-15 09:53:05 UTC (rev 831)
@@ -3,7 +3,7 @@
Copyright Notice and Statement for NCSA Hierarchical Data Format (HDF)
Software Library and Utilities
-Copyright 1988-2000 The Board of Trustees of the University of Illinois
+Copyright 1988-2005 The Board of Trustees of the University of Illinois
All rights reserved.
Modified: packages/libhdf4/branches/upstream/current/INSTALL
===================================================================
--- packages/libhdf4/branches/upstream/current/INSTALL 2007-05-15 09:05:29 UTC (rev 830)
+++ packages/libhdf4/branches/upstream/current/INSTALL 2007-05-15 09:53:05 UTC (rev 831)
@@ -1,1176 +1,158 @@
-***************************************************************************
- CONTENTS
- --------
- 1. Obtaining the latest version
+ Installation instructions for HDF4.2r1 on UNIX and MacOSX platforms
+ ====================================================================
+ February 2005
- 2. Installing HDF
- 2.1 Supported Platforms
- 2.2 Third Party Software Requirements
- 2.3 System Requirements
- 2.4 General Configuration/Installation - Unix
- 2.4.1 Overview
- 2.4.2 Layout of configuration files
+CONTENTS
- 2.4.3 Changing default values(CC,CFLAGS,..) and Setting Options
- 2.4.3.1 Changing default values(CC,CFLAGS,..)
- 2.4.3.2 Using HDF/MFHDF libraries w/ original netCDF library
- 2.4.3.3 Setting other Options
+0. Third Party Software Requirements
+1. Optional SZIP compression Library
+2. HDF4 Source code and precompiled binaries
+3. UNIX and MacOSX configuration and build
+4. Using HDF/MFHDF libraries w/ original netCDF library
- 2.4.4 Running configure
- 2.4.5 Dealing with Configure Problems
- 2.4.6 Compiling, Testing and Installing
- 2.5 Platform-specific Notes
- 2.5.1 Solaris on Sparc
- 2.5.2 Solaris on INTEL(x86)
- 2.5.3 OpenVMS AXP on DEC Alpha
- 2.5.4 Windows 98/NT/2000
- 2.5.5 Macintosh OS - Power PC ** Not Supported **
- 2.5.6 Exemplar
- 2.5.7 SP2 Single node
- 2.5.8 T3E Single node
- 2.5.9a SGI IRIX 6.x
- 2.5.9b SGI IRIX64
- 2.5.10 DEC Alpha
+0. Third Party Software Requirements
+ =================================
- 2.6 Pablo Instrumentation
- 2.7 File Cache(Beta release)
- 2.8 Installation Location
- 2.9 Specifying the System Type
- 2.10 Configure Options
+ x JPEG distribution release 6b(libjpeg.a). The "official" site
+ for this is ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz
- 3. Man pages
+ x ZLIB 1.1.4(libz.a) Source code and binaries may be downloaded from
+ http://www.gzip.org/ or from the NCSA ftp server
+ ftp://hdf.ncsa.uiuc.edu/lib-external/gzip/
+ Newest ZLIB 1.2 may also be used.
- 4. Release Notes
- 5. Documentation
+1. Optional SZIP compression Library
+ ==================================
- 6. FAQ
+ x HDF4.2r1 may be configured to use the SZIP compression Library.
+ For more information about the SZIP library, see
- 7. Java Products
+ http://hdf.ncsa.uiuc.edu/doc_resource/SZIP/
- 8. HELP
+ The SZIP compression library is free for non-commercial use;
+ see http://hdf.ncsa.uiuc.edu/doc_resource/SZIP/Commercial_szip.html
+ for information regarding commercial use.
+
+2. HDF4 Source code and precompiled binaries
+ ==========================================
+ HDF provides "tar source ball" and precompiled binaries from
+ the NCSA ftp server (ftp.ncsa.uiuc.edu) in the directories:
-*****************************************************************************
+ ftp://hdf.ncsa.uiuc.edu/HDF/HDF_Current/src
+ ftp://hdf.ncsa.uiuc.edu/HDF/HDF_Current/bin
-1. Obtaining the latest version
- ============================
+ IMPORTANT:
+ ==========
+ HDF4 prebuilt binaries come with the SZIP compression. In order to use
+ the binaries install SZIP Library on your system. You may download SZIP
+ precompiled binaries from
+ http://hdf.ncsa.uiuc.edu/doc_resource/SZIP
- The most recent version of the distribution can be obtained from
- the NCSA ftp archive site at:
- ftp://ftp.ncsa.uiuc.edu/HDF/HDF/HDF_Current/
+3. UNIX and MacOSX configuration and build
+ =======================================
- The HDF home page is at:
- http://hdf.ncsa.uiuc.edu/
+ 0) The HDF4.2r1 Library was tested on the following platforms
- The distribution can be downloaded from the HDF Home page at:
- http://hdf.ncsa.uiuc.edu/obtain.html
-
+ AIX 5.1, 5.2 (32 and 64-bit versions)
+ SunOs 5.7 (32 and 64-bit versions)
+ SunOS 5.8 (32 and 64-bit versions)
+ SunOS 5.9 (32 and 64-bit versions)
+ HPUX 11.00
+ Linux 2.4
+ IRIX64-6.5 (32 and 64-bit versions)
+ MacOSX
+ Crays SV1 and T90
+ True64 (OSF1 V5.1)
+ Windows 2000 and XP
+ FeeBSD
+ IA32 and IA64
+ Altix
+ AMD Opteron
-2. Installing HDF
- ==============
-
- For compiling and installing the HDF libraries, tests and
- utilities on a system, please follow these instructions.
-
-2.1 Supported Platforms
- ===================
-
- For PLATFORM specific NOTES see Section 2.5 called
- 'Platform-specific Notes'.
-
-
- Platform(OS) C-Compiler Fortran-Compiler
- ------------ ---------- ----------------
- Sun4(Solaris 2.7) WorkShop WorkShop Compilers 5.0
- Compilers C 5.0 FORTRAN 77 5.0
- Sun4(Solaris 2.6) WorkShop WorkShop Compilers 5.0
- Compilers C 5.0 FORTRAN 77 5.0
- SGI-Indy(IRIX v6.5) CC 7.30 f77 7.30
- SGI-Origin(IRIX64 v6.5-n32) CC 7.3.1m f77 7.3.1m
- SGI-Origin(IRIX64 v6.5-64) CC 7.3.1m f77 7.3.1m
- HP9000/755(HP-UX B.11.00) CC A.11.00.13 f77 B.11.00.01
- Exemplar(HP-UX B.10.01) CC V2.0 f77 V1.2.6
- Cray J90 (bob.1 10.0.0.7) CC 6.3.0.2 Cray Fortran 3.4.0.1.0
- IBM SP (single node, v4.3) XLC 5.0.1.0 f77 07.01.0000.0002
- DEC Alpha/Digital Unix v4.0 DEC C v5.2-040 Digital Fortran v4.1-92
- DEC Alpha/OpenVMS AXP v7.1 DEC C v5.6-003 Digital Fortran 77 X7.1-156
- IBM PC - Intel Pentium
- Solarisx86 (2.5.1) GCC 2.7.2 -
- Linux (2.2.16) GCC 2.95.2 g77 0.5.25
- FreeBSD (4.1.1) GCC 2.95.2 GNU f77 V0.5.25
- Windows NT/98/2000 MSVC++ 6.0 DEC Visual Fortran 6.0
- T3E (sn6711 2.0.539b) Cray CC 6.3.0.2 Cray Fortran 3.4.0.1.0
-
-
- NOTE: Platforms listed with compiler information entered, are
- platforms that HDF was tested on and for which we provide
- pre-compiled binaries.
-
-
-2.2 Third Party Software Requirements:
- ==================================
-
- 1. IJPEG distribution release 6b(libjpeg.a). The "official" site
- for this is ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz
-
- 2. ZLIB 1.1.3(libz.a) distribution.
-
- Both of these distributions are included with this distribution
- in 'hdf/jpeg' and 'hdf/zlib'. The HDF/mfhdf base distribution
- is known to work with these versions only.
-
-2.3 System Requirements
- ===================
-
- To build HDF from source, you need:
-
- * an ANSI C compiler. The native ANSI compilers on the above
- platforms are supported. On platforms where no ANSI compiler
- was available the free GNU ANSI compiler GCC was used.
-
- * a Fortran 77 compiler (F90 on Crays) if you want Fortran support.
- See above table for platforms where Fortran is supported. You
- can compile both libraries without Fortran support by setting
- the Fortran compiler variable 'FC = NONE' in the respective
- makefile fragment(mh-<os>) found in the top-level 'config'
- directory:
-
- $(toplevel)/config/mh-<os>.
-
- See below for further details of configuration and installation.
-
-
-2.4 General Configuration/Installation - Unix
- =========================================
-
- 2.4.1 Overview
- --------------
- In this distribution there are two types of 'configure'
- scripts. One is the Cygnus 'configure' script and the other is the
- 'configure' script created by the GNU autoconf package. The Cygnus
- 'configure' script is used at the top level to configure the overall
- distribution and the HDF/MFHDF/IJPEG/ZLIB libraries. The GNU 'configure'
- script is used by the netCDF/IJPEG distributions to configure themselves.
- However, these gnu configure scripts are not used in configuring this
- distribution.
-
- The Cygnus 'configure' script attempts to guess the correct
- platform you are configuring the distribution for by calling the shell
- script 'config.guess'. It outputs a unique string based on information
- obtained from the UNIX command 'uname' consisting of CPU-VENDOR-OS
- e.g. 'hppa1.1-hp-hpux9.03' for an HP9000/735 running HPUX-9.03.
-
- 2.4.2 Layout of configuration files
- -----------------------------------
- The following shows the layout of the files used in the configuration
- of the HDF distribution.
-
- NOTE: The $(toplevel)/mfhdf/CUSTOMIZE and
- $(toplevel)/mfhdf/configure(autoconf) files are no longer used
- in the configuration of the distribution.
-
- $(toplevel)/Makefile.in
- config.guess
- config.sub
- configure (cygnus)
- configure.in (cygnus)
- config/mh-hpux, mh-sun,.....(host makefile fragments)
-
- man/Makefile.in
-
- mfhdf/CUSTOMIZE(not used)
- mfhdf/configure(autoconf - not used)
- mfhdf/libsrc/config/netcdf-aix.h,... -> copied to netcdf.h
- mfhdf/fortran/config/ftest-aix.f,... -> copied to ftest.f
- mfhdf/fortran/config/jackets-aix.c,.. -> copied to jackets.c
- mfhdf/fortran/config/netcdf-aix.inc,..-> copied to netcdf.inc
-
- hdf/Makefile.in
- hdf/src/Makefile.in
- hdf/test/Makefile.in
- hdf/util/Makefile.in
- hdf/zlib/Makefile.in
- hdf/pablo/Makefile.in
-
- hdf/jpeg/configure.in (cygnus)
- hdf/jpeg/Makefile.in
- hdf/jpeg/configure.gnu(autoconf - not used)
- hdf/jpeg/config/mh-hpux, mh-sun,... (host makefile fragments)
- hdf/jpeg/config/jhpux.h, jsun.h,... -> copied to jconfig.h
-
- hdf/fmpool/configure, configure.in config.guess, config.sub,
- Makefile.in (all cygnus)
- hdf/fmpool/config/mh-hpux, mh-sun,...(host makefile fragments)
- hdf/fmpool/config/fmpsolaris.h,... -> copied to fmpconf.h
-
- 2.4.3 Changing default values(CC,CFLAGS,..) and Setting Options
- ---------------------------------------------------------------
- To change any of the default values or set any of the options
- edit the makefile fragment:
-
- $(toplevel)/config/mh-<os>
-
- for your particular operating system. After changing the values you must
- re-run the top-level 'configure' script. Make sure you start from
- a clean distribution if you are rebuilding after a previous make
- (i.e. 'make distclean') before re-running 'configure'.
-
- 2.4.3.1 Changing default values(CC,CFLAGS,..)
- ********************************************
- To change any of the default values for CC, FC, CFLAGS, FFLAGS,..etc
- edit the top part of the makefile fragment: $(toplevel)/config/mh-<os>
- It is also a good idea to look at the other system variables to make sure
- they are set correctly for your system.
-
- 2.4.3.2 Using HDF/MFHDF libraries w/ original netCDF library
- ************************************************************
- To use the HDF/MFHDF libraries(libdf.a, libmfhdf.a) with the
- original netCDF library(libnetcdf.a) the HDF/MFHDF distribution
- must be compiled with the option '-DHAVE_NETCDF'. This will
- rename the HDF version of the C-interface(ncxxx) of the netCDF API
- to sd_ncxxx to avoid clashing with the original netCDF API from
- libnetcdf.a. Currently there is no support for renaming the
- netCDF Fortran interface stubs. As such the HDF/MFHDF distribution
- must be compiled without fortran support. HDF Users can still access
- HDF/netCDF files through the SDxxx interface but not through the
- ncxxx interface unless the renamed interface is used(sd_ncxxx).
-
- 2.4.3.3 Setting other Options
- *****************************
- The makefile fragment must also be modified to enable the features
- mentioned in sections 2.6) and 2.7) below.
-
- 2.4.4 Running configure
- -----------------------
- To build both of the libraries contained in this directory,
- run the ``configure'' script in $(toplevel), e.g.:
-
- ./configure -v --prefix=/usr/local/hdf
-
- If you're using `csh' on an old version of System V, you might need
- to type `sh ./configure -v --prefix=/usr/local/hdf' instead to prevent
- `csh' from trying to execute `configure' itself.
-
- This will configure the distribution to install the libraries, utilities,
- include and man files in '/usr/local/hdf/lib','/usr/local/hdf/bin',
- '/usr/local/hdf/include' and '/usr/local/hdf/man' respectively. The
- default 'prefix' is '/usr/local'. It is advisable to use something
- like the above to avoid overwriting say another 'libjpeg.a' that might be
- installed in '/usr/local/lib'. The '-v' option is for verbose output.
-
- Note that both 'libz.a' and 'libjpeg.a' and their respective
- include files are installed along with the base HDF(libdf.a)
- and netCDF(libmfhdf.a) libraries.
-
- If the configure script can't determine your type of computer
- then it probably is a platfrom that is no longer supported.
- If you want to be adventurous see the section 'Dealing with
- Configure Problems' below. Otherwise send an email to
- 'hdfhelp at ncsa.uiuc.edu' for further help.
-
- 2.4.5 Dealing with Configure Problems
- *************************************
- If you want to be adventurous you can try the following.
-
- Configure basically calls either of the two shell scripts 'config.guess'
- or 'config.sub' depending upon whether a target platform was supplied
- on the command line to configure. If you don't provide a target on
- the command line configure calls 'config.guess' to guess what platfrom
- it is configuring for. The shell script 'config.guess' uses the unix
- command 'uname' to figure out the CPU, vendor, and OS of the
- platform. If you do provide a target on the command line, configure
- calls the shell script 'config.sub' to build the triplet specifying
- CPU, vendor, and OS from the full or partial target provided.
-
- If the configure script can't determine your type of computer, give it
- a general name that the computer is generally referred to as an argument,
- for instance './configure sun4'. You can use the script 'config.sub'
- to test whether a general name is recognized; if it is, config.sub
- translates it to a triplet specifying CPU, vendor, and OS.
- (e.g hppa1.1-hp-hpux9.03 for an HP900/735 running HPUX9.03).
-
- If this still fails all is not lost. All the configure script really
- needs is one of the supported targets mentioned above(except NT).
- If you think your platform is close to one of the above platforms
- mentioned in the 'Supported Platforms' sections you can pass configure
- this target and it will configure the distribution for that target.
-
- For possible mappings you will need to look inside the shell script
- 'config.sub' and look at the partial to full mappings and pick one
- that satisfies the triplet mappings found in 'configure.in' below
- the section "# per-host:'. Note that if you try a mapping and it
- does not work this means that 'config.sub' needs to be edited to
- provide the proper mapping from your target to a full mapping that
- is supported.
-
- There are currently NO instructions for porting the distribution to a
- new platform.
-
- 2.4.6 Compiling, Testing and Installing
- ---------------------------------------
- To compile the library and utilities type:
-
- make
-
- To find out the available make targets type:
-
- make help
-
- To test the libraries and utilities type:
-
- make test
-
- It is a good idea to save the output of the tests and view it later
- for errors.
- e.g.
-
- make test >& make.test.out
-
- To install the libraries, utilities, includes and man pages type: e.g.
-
- make install
-
-2.5 Platform-specific Notes
- ========================
-
-
- 2.5.1 Solaris on Sparc
- ----------------------
- The distribution has been compiled/tested with the native
- ANSI-C compiler and native fortran compiler. The binary
- distribution was compiled using the native compilers.
-
- When compiling your programs on Solaris, you must include the
- the nsl library, to resolve calls to the xdr* routines.
- For example,
-
- cc -Xc -xO2 -o <your program> <your program>.c \
- -I<path for hdf include directory>\
- -L<path for hdf libraries> -lmfhdf -ldf -ljpeg -lz \
- -L/usr/lib -lnsl
-
-
- 2.5.2 Solaris on INTEL(x86)
- ---------------------------
-
- The distribution has been compiled/tested with GCC 2.7.2 with
- *NO* FORTRAN support.
-
- When compiling your programs on Solaris_x86, you must include the
- the nsl library, to resolve calls to the xdr* routines.
- For example,
-
- gcc -ansi -O -o <your program> <your program>.c \
- -I<path for hdf include directory> \
- -L<path for hdf libraries> -lmfhdf -ldf -ljpeg -lz \
- -L/usr/lib -lnsl
-
- 2.5.3 OpenVMS AXP on DEC Alpha
- ------------------------------
-
- To build the HDF Library on Alpha OpenVMS systems use
- MAKEVMS.COM file in the top level directory of the VMS Library source.
- -------------------
-
- To build the library in interactive mode run
-
- @MAKEVMS.COM
-
- To build the library in the background:
-
- 1. Check that the first command in MAKEVMS.COM sets default directory
- to the top level directory in the HDF Library source tree (just
- edit the first command line: $ set def.... ).
-
- 2. Submit MAKEVMS.COM to the appropriate batch queue on your system
- For example:
-
- $ submit/log=buildhdf.log/noprint/notify/restart/que=batch$queue MAKEVMS.COM
-
-
- MAKEVMS.COM file
-
- 1. Creates three directories in the top level directory:
- [...tophdf.include]
- [...tophdf.bin]
- [...tophdf.lib]
-
- 2. Builds four libraries LIBJPEG.OLB, LIBZ.OLB, DF.OLB, and MFHDF.OLB,
- and copies them into the [...tophdf.bin] directory.
-
- 3. Builds the HDF utilities and copies them into the [...tophdf.bin]
- directory.
-
- 4. Copies the header files to the [...tophdf.include] directory.
-
- 5. Runs the library tests after building each library and the tests for the
-
- ncdump, ncgen and hdp utilities.
-
- We recommend building the library in background and then checking log file
- for test results. Output of the hdp test is written to the
- [...tophdf.mfhdf.dumper]hdp.out file.
-
- See MAKEVMS.COM for more information.
-
- NOTE: If you are building from UNIX source perform the following steps
- before you run MAKEVMS.COM:
-
- 1. Make sure that files in the directory [.mfhdf.fortran.vms] are
- up to date.
- 2. In the directory [.hdf.test] change the files
- forsupff.f
- tsdmmsf.f
- tsdnmmsf.f
- tsdntf.f
- tsdnnt.f
- tvsetf.f
- slabwf.f
- following the instructions given in the comments,
- which start with 'For VMS', in these files.
-
-
- 2.5.4 Windows 98/NT/2000
- ------------------------
-
- Install HDF4.1 Release 4 on Windows NT, Windows 2000 and Windows 98
-
-The instructions which follow assume that you will be using one of
-the 'zip' files that we provide, either the binary code release
-(HDF41r4.zip) or the source code release (HDF41r4s.zip).
-
-In building HDF from source code you may select between
-two build environment options ( with Fortran or without Fortran support
-depending on your application and environment needs ).
-
-The following sections discuss in details installation procedures.
-
-
-Building from Binary Code Release (HDF41r4.zip)
-===============================================
-To install the HDFand MFHDF libraries and utilities,
-it is assumed that you have done the following:
+ For more information, see the release_notes/RELEASE.txt file, "Platforms
+ tested" section.
-
- 1. Create a directory structure to unpack the library. For
- example:
-
- c:\ (any drive)
- MyHDFstuff\ (any folder name)
-
- 2. Copy the binary archive (HDF41r4.zip)
- to that directory
- and unpack it by running WinZip on HDF41r4.zip (the binary archive).
- This should create a directory called 'HDF41r4' which
- contains the following files and directories.
-
- c:\MyHDFstuff\HDF41r4\lib ( Single-threaded static
- versions of HDF and MFHDF
- libraries with Fortran
- or without Fortran support )
- c:\MyHDFstuff\HDF41r4\dlllib ( Multi-threaded DLL import
- HDF and MFHDF libraries
- and DLL files with Fortran
- or no Fortran support )
- c:\MyHDFstuff\HDF41r4\include ( include files )
- c:\MyHDFstuff\HDF41r4\bin ( utilities )
- c:\MyHDFstuff\HDF41r4\release_notes ( release notes )
- c:\MyHDFstuff\HDF41r4\install_NT_98 ( this file)
-
-
- 3. If you are building an application that uses the HDF libraries
- the following locations will need to be specified for locating
- header files and linking in the HDF libraries:
+ Before you start:
- C:\MyHDFstuff\HDF41r4\lib or C:\MyHDFstuff\HDF41r4\dlllib
- C:\MyHDFstuff\HDF41r4\include
+ 1) Make sure that the ZLIB and JPEG Libraries are installed on your
+ system.
+ 2) Optional: install the SZIP version 2.0 Library.
+ 3) Extract the source from the hdf4.2r1.tar file and change
+ directory to hdf4.2r1
+ To Configure:
+ 4) Use the configure command in the top level HDF4 directory hdf4.2r1
-Note: The ws2_32.lib needs to linked with your executable if using the static
- mfhdf library. The ws2_32.lib can be found in your Microsoft Visual C++
- directory under the lib folder.
+ ./configure --with-zlib=/path_to_ZLIB_install_directory
+ --with-jpeg=/path_to_JPEG_install_directory
+ <--with-szlib=/path_to_SZIP_install_directory>
+ --prefix=/path_to_HDF4_install_directory
+ * Please note that when szlib option is not used, SZIP Library will not
+ be configured in and SZIP compression will not be enabled.
+ * If your system has ZLIB and/or JPEG libraries installed under a
+ system library directory (such as /usr/lib), configure will
+ automatically find the library. In this case, the corresponding
+ configure flag may be ommitted.
+ * Note that --prefix defines where the installation path is.
+ The default is set as <hdf4_build_directory>/NewHDF
-Building from Source Code Release (HDF41r4s.zip)
-================================================
+ To Build and Test:
-STEP I: Preconditions
+ 5) To build the library
-To build the HDF and MFHDF libraries ( single-threaded static or
-multi-threaded DLL import libraries) and utilities,
-it is assumed that you have done the following:
-
- 1. Installed MicroSoft Developer Studio, and Visual C++ 6.0.
- Visual Fortran 6.0 is needed if you are going to build the
- full HDF Library with Fortran support.
+ gmake >& gmake.out
- 2. Set up a directory structure to unpack the library. For
- example:
+ 6) To build and run the tests
- c:\ (any drive)
- MyHDFstuff\ (any folder name)
+ gmake check >& check.out
- 3. Copy the source distribution archive to that directory
- and unpack it using the appropriate archiver options to
- create a directory hierarchy.
-
- Run WinZip on HDF41r4s.zip (the entire source tree).
- This should create a directory called 'HDF41r4' which
- contains several files and directories.
-
-Note: If you are building from the UNIX source code, then you will
- need to replace the jconfig.h and netcdf.h file as follows
- ( this assumes that the HDF Library tree resides
- under HDF41r4 directory ):
-
- copy C:\MyHDFstuff\HDF41r4\hdf\jpeg\config\jwin32.h
- C:\MyHDFstuff\HDF41r4\hdf\jpeg\jconfig.h
- copy C:\MyHDFstuff\HDF41r4\mfhdf\libsrc\win32cdf.h
- C:\MyHDFstuff\HDF41r4\mfhdf\libsrc\netcdf.h
+ To Install:
-You do not need to do this if you are using the HDF41r4s.zip file!
+ 7) To install the HDF4 library and tools
-STEP II: Select Installation type and Build.
+ gmake install
-You may select one of 2 ways to build the HDF libraries and
-utilities, depending on your environment and application needs.
-
-Option I, (select Win32.nofortran.zip)
-This is the "NOFORTRAN" configuration : It builds debug and release single-threaded
-and multi-threaded versions of the HDF libraries, tests, and utilities.
-There is no Fortran support.
-
-
-Option II, (select Win32.zip)
-This is "WITH FORTRAN support" configuration : it is the same as above but with
-Fortran support.
-
-
-
-STEP III: Building the Libraries, tests and utilities.
-Note that the instructions are the same for both Options I and II.
-
-
- 1. Unpack Win32.nofortran.zip or Win32.zip in
- directory HDF41r4\.
-
- 2. Invoke Microsoft Visial C++ 6.0, go to "File" and select
- the "Open Workspace" option.
- Then open the c:\myHDFstuff\HDF41r4\all.dsw workspace.
-
- 3. Select "Build", then Select "Set Active Configuration".
-
- On Windows platform select as the active configuration
-
- "all -- Win32 Debug" to build debug versions of single-threaded
- static libraries, tests and utilities and
- multi-threaded libraries and tests.
- or
+ 8) By default the current configuration uses vendor compilers; to use
+ another compiler run the following commands before running
+ configure:
- "all -- Win32 Release" to build release versions of single-threaded
- static libraries, tests and utilities and
- multi-threaded libraries and tests.
-
-
- Select "Build" and "Build all.exe" to
- build the corresponding version of the HDF41r4 library.
- If you are building from the Win32.zip archive,
- you will see that the Digital Visual Fortran compiler is invoked
- by the Visual C++ Development environment in compiling the fortran code.
-
- NOTE: "all" is a dummy target. You will get a link error when
- "all.exe." is built :
- LINK: error LNK2001: unresolved external symbol _WinMainCRTStartup.....
- all.exe - 2 error(s), ....
-
- Warning messages can be ignored. The "all.exe" is never created,
- so it is OK.
-
- When the debug build is done the directories listed
- below will contain the following files:
-
- c:\MyHDFstuff\HDF41r4\Windows\bin\debug -
-
- utilities, statically linked with the single-threaded libraries.
-
- c:\MyHDFstuff\HDF41r4\Windows\lib\debug\singlethreaded -
-
- HD414d.lib - HDF static library (inludes JPEG and GZIP libraries)
- HM414d.lib - MFHDF static library
-
- c:\MyHDFstuff\HDF41r4\Windows\lib\debug\multithreaded -
-
- HD414md.lib - HDF multi-threaded DLL import library
- (inludes JPEG and GZIP libraries)
- HM414md.lib - MFHDF multi-threaded DLL import library
-
- c:\MyHDFstuff\HDF41r4\Windows\DLL\debug
-
- HD414md.DLL - HDF DLL
- HM414md.DLL - MFHDF DLL
-
- When the release build is done the directories listed
- below will contain the following files:
+ setenv CC "foo -flags"
+ setenv F77 "fffoo -flags"
- c:\MyHDFstuff\HDF41r4\Windows\bin\release -
-
- utilities, statically linked with the single-threaded libraries.
-
- c:\MyHDFstuff\HDF41r4\Windows\lib\release\singlethreaded -
-
- HD414.lib - HDF static library (inludes JPEG and GZIP libraries)
- HM414.lib - MFHDF static library
+ See the configure help page (configure --help) for a list of
+ environment variables that have an affect on building the
+ library.
- c:\MyHDFstuff\HDF41r4\Windows\lib\release\multithreaded -
-
- HD414m.lib - HDF multi-threaded DLL import library
- (inludes JPEG and GZIP libraries)
- HM414m.lib - MFHDF multi-threaded DLL import library
-
- c:\MyHDFstuff\HDF41r4\Windows\DLL\release
+ 9) You may build HDF4 in a directory other than hdf4.2r1 by
+ using the "srcdir" option. Simply create a build directory and
+ type:
- HD414m.DLL - HDF DLL
- HM414m.DLL - MFHDF DLL
+ <path_to_hdf4.2r1>/configure ...
-
-Note: The ws2_32.lib needs to linked with your executable if using the static
- mfhdf library. The ws2_32.lib can be found in your Microsoft Visual C++
- directory under the lib folder.
-
-
-STEP IV: TESTING THE BUILD
-
- In a command prompt window run the test batch file which
- resides in the HDF41r4 directory to make sure that the libraries
- were built correctly.
-
- Set the path to include the DLL files or copy the files to the system
- directory.
-
- Then run Win32debugtst.bat to test debug version or
- Win32releasetst.bat to test release version.
-
-
-STEP V: INSTALLATION
-
- In the command prompt window run the install_debug.bat file to install
- the debug version. This file will create four directories under
- the HDF41r4 directory and copy over corresponding files:
-
- bindbg - utilties
- libdbg - static libraries
- dlllibdbg - multi-threaded libraries and DLLs
- include - include files
-
- In the command prompt window run install_release.bat file to install
- release version. This file will create four directories under HDF41r4
- directory and copy corresponding files:
+ where "..." are your configuration options.
- bin - utilties
- lib - static libraries
- dlllib - multi-threaded libraries and DLLs
- include - include files
-
-Note: There is an error in the debug version of the hdp tool. It will show an
- alert box with the error and 3 buttons. This is a known problem. The release
- version is fine.
+4. Using HDF/MFHDF libraries w/ original netCDF library
+ ====================================================
-STEP VI:
+ To use the HDF/MFHDF libraries(libdf.a, libmfhdf.a) with the
+ original netCDF library(libnetcdf.a) the HDF/MFHDF distribution
+ must be compiled with the option '-DHAVE_NETCDF'. This will
+ rename the HDF version of the C-interface(ncxxx) of the netCDF API
+ to sd_ncxxx to avoid clashing with the original netCDF API from
+ libnetcdf.a. Currently there is no support for renaming the
+ netCDF Fortran interface stubs. As such the HDF/MFHDF distribution
+ must be compiled without fortran support. HDF Users can still access
+ HDF/netCDF files through the SDxxx interface but not through the
+ ncxxx interface unless the renamed interface is used(sd_ncxxx).
-BUILDING AN APPLICATION USING THE HDF LIBRARY - SOME HELPFUL POINTERS
-=====================================================================
-If you are building an application that uses the HDF library
-the following locations will need to be specified for locating
-header files and linking in the HDF libraries:
-
- <top-level HDF directory>\lib
- <top-level HDF directory>\dlllib
- <top-level HDF directory>\include
-where <top-level HDF directory> may be C:\myHDFstuff\dev or C:\MyHDFstuff\HDF41r4\
+ Report all problems to hdfhelp at ncsa.uiuc.edu
-
-Using Microsoft Visual C++ version 6.x:
-
-Under Tools->Options, select the folder, Directories:
- Under "Show directories for", select "Include files".
- Add the following directories:
- C:<path to HDF includes>\include
-
-Under "Show directories for", select "Library files":
- Add the following directories:
- C:<path to HDF libs>\lib
-
-Under Project->Settings, select folder, Link:
- Add the following libraries to the beginning of the list of
- Object/Library Modules:
- HD414.lib HM414.lib (single-threaded release version)
- HD414d.lib HM414d.lib (single-threaded debug version)
-
- HD414m.lib HM414m.lib (multi-threaded release version)
- HD414md.lib HM414md.lib (multi-threaded debug version)
-
-
-MORE HELPFUL POINTERS
-=====================
-(as described in terms of installing the nofortran configuration)
-
-Here are some notes that may be of help if you are not familiar
-with using the Visual C++ Development Environment.
-
-Project name and location issues:
- The files in Win32.zip and Win32.nofortran.zip must end up
- in the HDF41r4\ directory installed by HDF41r4s.zip
-
- If you must install all.dsw and all.dsp in
- another directory, relative to HDF41r4\ , you will be asked to
- locate the above 5 sub-project files, when you open the
- project all.dsw.
-
- If you want to rename all (the entire project),
- you will need to modify two files
- all.dsw and all.dsp as text
- (contrary to the explicit warnings in the files).
-
- You can also modify all.dsw and all.dsp
- as text, to allow these 2 files to be installed
- in another directory.
-
-
-
- Settings... details:
- If you create your own project, the necessary settings can be
- read from the all.dsp file(as text), or from the
- Project Settings in the Developer Studio project settings
-dialog.
-
- Project
- Settings
- C/C++
- Category
- PreProcessor
- Code Generation
- Use run-time Library
- These are all set to use
- Single-Threaded
- or Single-Threaded debug
- or Multi-Threaded
- or Multi-Threaded debug
-
-
-
-
-
- 2.5.5 Macintosh OS - Power PC -
- -------------------------------
- **** NOT SUPPORTED WITH HDF 4.1r4 ****
-
- The distribution was compiled/tested with MetroWerks Codewarrior(CW Pro1).
- Only the base libraries {jpeg.PPC.lib, z.PPC.lib, hdflib.PPC.lib,
- xdr.PPC.lib and mfhdf.PPC.lib} were compiled and tested on the
- PowerPC without Fortran support.
-
- *NO* Fortran support is included in this distribution.
-
- Codewarrior Projects can be found with this distribution.
- They have been run through the Macintosh BinHex utility program.
- You need to compile the libraries before you can compile the test
- programs 'testhdf', 'xdrtest', 'cdftest', 'hdftest' and 'nctest'.
-
- 2.5.5.1 Special Notes
- *********************
- 1. The test programs are SIOUX applications.
-
- 2. When testing 'testhdf' in the 'hdf/test' directory make sure
- that a directory called 'testdir' exists in 'hdf/test'.
- This directory is used in the external element test.
-
- 3. You need at least 8MB of memory to run most of the test programs.
-
- 4. Distribution also contains projects files to build utilities,
- but utilities were not tested.
-
- 2.5.5.2 Building the Distribution
- *********************************
- The distribution and tests need to be built in the order specified below.
- Codewarrior Projects with the targets for Power PC and 68K can be
- found in the following directories:
-
- $(toplevel)/
- hdf/zlib/zlib.project.hqx
-
- hdf/jpeg/jpeglib.project.hqx
-
- hdf/src/hdflib.project.hqx
-
- hdf/test/testhdf.project.hqx
-
- hdf/test/testdir(need to create this if it does not exist)
-
- mfhdf/xdr/xdrlib.project.hqx
- mfhdf/xdr/xdrtest.project.hqx
-
- mfhdf/libsrc/mfhdflib.project.hqx
- cdftest.project.hqx
- hdftest.project.hqx
-
- mfhdf/nctest/nctest.project.hqx
-
- Note that only the PPC version of the libraries and tests are supported.
-
- 2.5.5.3 Testing the Distribution
- ********************************
- Run the tests in the following order:
-
- 1. hdf/test/testhdf
- Note:
- When testing 'testhdf' in the 'hdf/test' directory make sure
- that a directory called 'testdir' exists in the 'hdf/test'.
- This directory is used in the external element test.
-
- 2. mfhdf/xdr/xdrtest
- After running this test compare the output to that shown in
- the file mfhdf/xdr/testout.sav
-
- 3. mfhdf/libsrc/hdftest
- After running this test compare the output to that shown in
- the file mfhdf/libsrc/hdfout.sav
-
- 4. mfhdf/libsrc/cdftest
- After running this test compare the output to that shown in
- the file mfhdf/libsrc/testout.sav
-
- 5. mfhdf/nctest/nctest
-
- 2.5.5.4 Building utilities
- ********************************
-
- Codewarrior Projects for utilities can be found in the following
- directories:
-
-
- $(toplevel)/
- mfhdf/dumper/hdp/hdp.project.hqx
-
- hdf/util/fp2hdf/fp2hdf.project.hqx
- hdf24to8/hdf24to8.project.hqx
- hdfcomp/hdfcomp.project.hqx
- hdfed/hdfed.project.hqx
- hdfls/hdfls.project.hqx
- hdfls/hdfls.project.hqx
- hdfpack/hdfpack.project.hqx
- hdftoPal/hdftopal.project.hqx
- hdftoR8/hdftoR8.project.hqx
- vshow/vshow.project.hqx
- PalToHDF/PalToHDF.project.hqx
- R8ToHDF/R8ToHDF.project.hqx
- RISToHDF/RISToHDF.project.hqx
-
- 2.5.6 Exemplar
- --------------
- HP Exemplar (Convex) machines running version 10.x of HP-UX are now only
- able to be configured for HP-UX. If you are running an Exemplar with an
- earlier version of the software, you must configure the machine as
- follows:
-
- ./configure -v --host=c2-convex-bsd
-
- Otherwise, the machine will be configured for HP-UX.
-
-
- 2.5.7 SP2 Single node
- ----------------------
- HDF has been compiled and tested to run in a single node of the
- SP2 system. You can make the library the same way you would on an
- AIX system. To use it in the parallel processing environment, we
- advise you to execute the HDF code in only one designated process
- since HDF code does not support concurrent access to the same file.
-
-
- 2.5.8 T3E Single node
- ---------------------
- HDF has been compiled and tested to run in a single node of the
- T3E system. It is compiled with the '-X m' to produce malleable
- code which can be executed with multiple processing elements (PEs).
- The code has not been tested run with multiple PEs. To use it in
- the parallel processing environment, we advise you to execute the
- HDF code in only one designated process since HDF code does not
- support concurrent access to the same file.
-
-
- NOTE: HDF is compiled with the f90 compiler starting release 4.1r2.
- Cray has phased out the cf77 compiler. The f90 compiler issues
- numerous warnings during the compiling of the Fortran API test
- programs. They can be safely ignored. One warning is about the
- unsupported DOUBLE PRECISION being replaced by REAL. That works fine
- for the purpose of the test programs since T3E REAL is 8 bytes in
- size which is the same size as DOUBLE PRECISION in other machines.
- Another warning is by the loader complaining about many SYMBOLS
- referenced but not defined. Those SYMBOLS are actually HDF Fortran
- function names declared in dffunc.inc file and they are not used in
- the testing.
-
-
- 2.5.9a SGI IRIX 6.x
- -------------------
- IRIX is the traditional SGI 32-bit OS. Starting in version 6.x,
- it supports two classes of 32 bit compilers, the old 32 (-o32)
- and the new 32-bits (-n32). SGI is phasing out the -o32 compilers.
- Continued maintenance is available on the -n32 class of compilers only.
- The HDF library configures to use the -n32 class of C and F77 compilers.
- If you want to use different compiler options, you need to edit
- config/mh-irix32 and then run configure. Consult the section
- of "General Configuration/Installation" for more information.
-
-
- 2.5.9b SGI IRIX64
- -----------------
- IRIX64 supports multiple combinations of ABI (-64, -n32, -o32) and
- instruction sets (-mips2, -mips3, -mips4). Previous HDF
- library releases had hard coded the MIPS settings by guessing what
- might be the most reasonable combination. This release no longer
- sets the MIPS option but leaves it up to the local or user's
- default. The configure still generates -64 code by default on
- an IRIX64 system. If -n32 code is desired, one may override it
- by specifying 'irix6_32' during the configure step.
-
- Configure command Code produced
- ----------------- -------------
- ./configure -64
- ./configure irix6_32 -n32
-
- If you want to use different compiler options, you need to edit
- config/mh-irix6 (for just configure) or config/mh-irix32 (for
- configure irix6_32) and then run configure. Consult the section
- of "General Configuration/Installation" for more information.
-
-
- 2.5.10 DEC Alpha
- ----------------
- The distribution has been compiled/tested with the native Digital
- Unix C and FORTRAN compilers.
-
- During the testing of the library the test 'mfhdf/libsrc/hdftest'
- will report "Unaligned access ..." messages which can be ignored.
-
-
-2.6 Pablo Instrumentation
- =====================
-
- This version of the distribution has support to create an instrumented
- version of the HDF libraries(libdf-inst.a and libmfhdf-inst.a). This
- library along with the Pablo performance data capture libraries can be
- used to gather data about I/O behavior and procedure execution times.
- Version 5.1 or higher of the trace library is required.
-
- More detailed documentation on how to use the instrumented version of
- the HDF library with Pablo can be found in the Pablo directory:
-
- $(toplevel)/hdf/pablo
-
- See the provided '$(toplevel)/hdf/pablo/README.Pablo' and the PostScript
- file '$(toplevel)/hdf/pablo/Pablo.ps' or Microsoft Word Document file
- '$(toplevel)/hdf/pablo/Pablo.doc' or the PDF document file
- /$(toplevel)/hdf/pablo/Pablo.pdf'.
-
- In this version both an instrumented version of the core HDF library
- libdf.a and the library libmfhdf.a can be created. Current interfaces
- supported are ANxx, GRxx, DFSDxx, DFANxx, DFPxx, DFR8xx, DF24xx, Hxx,
- SDxx, Vxx, and VSxx.
-
- To enable the creation of an instrumented library the following section
- in the makefile fragment($(toplevel)/config/mh-<os>) must be uncommented
- and set.
-
- # ------------ Macros for Pablo Instrumentation --------------------
- # Uncomment the following lines to create a Pablo Instrumentation
- # version of the HDF core library called 'libdf-inst.a'
- # See the documentation in the directory 'hdf/pablo' for further
- # information about Pablo and what platforms it is supported on
- # before enabling.
- # You need to set 'PABLO_INCDIR' to the Pablo distribution
- # include directory to get to files 'IOTrace.h', 'IOTrace_SD.h' and others.
- #PABLO_FLAGS = -DHAVE_PABLO
- #PABLO_INCDIR = /usr/local/include/pablo-5.1
- #PABLO_INCLUDE = -I$(PABLO_INCDIR)
- After setting these values you must re-run the toplevel 'configure' script.
- Make sure that you start from a clean re-build(i.e. 'make clean') after
- re-running the toplevel 'configure' script and then run 'make'.
- Details on running configure can be found above in the section
- 'General Configuration/Installation - Unix'.
-
-2.7 File Cache(Beta release)
- =================================
- This version of the distribution has preliminary support for file caching.
-
-*NOTE*: This version is NOT officially supported on all platforms
- and has not been extensively tested. As such it is provided as is.
- It will be supported officially in a later release.
-
- The file cache allows the file to be mapped to user memory on
- a per page basis i.e a memory pool of the file. With regards to the
- file system, page sizes can be allocated based on the file system
- page-size or if the user wants in some multiple of the file system
- page-size. This allows for fewer pages to be managed along with
- accommodating the users file usage pattern.
-
- The current version supports setting the page-size and number of pages
- in the memory pool through user C-routines(Fortran will be added in a
- future release). The default is 8192 bytes for page-size and 1 for number
- of pages in the pool.
-
- Routines:(The names may change in the future...)
- -------------------------------------------------
- Hmpset(int pagesize, int maxcache, int flags)
- --------------------------------------------
- o Set the pagesize and maximum number of pages to cache on the next
- open/create of a file. A pagesize that is a power of 2 is recommended.
- 'pagesize' must be greater than MIN_PAGESIZE(512) bytes and
- 'maxcache' must be greater than or equal to 1. Valid values
- for both arguments are required when using this call.
-
- The values set here only affect the next open/creation of a file and
- do not change a particular file's paging behavior after it has been
- opened or created. This may change in a later release.
-
- Use flags argument of 'MP_PAGEALL' if the whole file is to be cached
- in memory otherwise pass in zero. In this case the value for 'maxcache'
- is ignored. You must pass in a valid value for 'pagesize' when
- using the flag 'MP_PAGEALL'.
-
- Hmpget(int *pagesize, int *maxcache, int flags)
- ----------------------------------------------
- o This gets the last pagesize and maximum number of pages cached for
- the last open/create of a file. The 'flags' variable is not used.
-
- In this version a new file memory pool is created for every file that is
- created/opened and can not be shared. Future versions will allow sharing
- of the file memory pool with other threads/processes.
-
- To enable the creation of a library using page caching the following
- section in the makefile fragment($(toplevel)/config/mh-<os>) must be
- uncommented and set.
-
- # ------------ Macros for Shared Memory File Buffer Pool(fmpool) ------
- # Uncomment the following lines to enable shared memory file buffer pool
- # version of the HDF core library libdf.a. Please read the
- # documentation before enabling this feature.
- #FMPOOL_FLAGS = -DHAVE_FMPOOL
-
- After setting these values you must re-run the toplevel 'configure' script.
- Make sure that you start from a clean re-build(i.e. 'make clean') after
- re-running the toplevel 'configure' script and then run 'make'.
- Details on running configure can be found above in the section
- 'General Configuration/Installation - Unix'.
-
- The file caching version of libdf.a is automatically tested
- when the regular HDF and netCDF tests are run. The page caching
- version has been tested only on a few UNIX platforms and is NOT
- available for the Macintosh ,IBM-PC(Windows NT/95) or VMS.
-
-2.8 Installation Location
- =====================
-
- By default, `make install' will install the HDF/mfhdf files in
- `$(toplevel)/NewHDF/bin', '$(toplevel)/NewHDF/lib', etc. You may
- then copy the files to the appropriate directories on your system.
- If you prefer, you can specify the directory so that `make install'
- will install the files directly in it. This is done by giving
- `configure' the option `--prefix=PATH'.
-
- eg. ./configure -v --prefix=/usr/local/hdf
-
- This will configure the distribution to install the libraries,
- utilities, include and man files in '/usr/local/hdf/lib',
- '/usr/local/hdf/bin', '/usr/local/hdf/include' and
- '/usr/local/hdf/man' respectively.
-
-2.9 Specifying the System Type
- ==========================
-
- There may be some features `configure' can not figure out
- automatically, but needs to determine by the type of host HDF/mfhdf
- will run on. Usually `configure' can figure that out, but if it prints
- a message saying it can not guess the host type, give it the
- `--host=TYPE' option. TYPE can either be a short name for the system
- type, such as `sun4', or a canonical name with three fields:
-
- CPU-COMPANY-SYSTEM
-
- e.g. hppa1.1-hp-hpux9.03
-
- See the file `config.sub' for the possible values of each field.
-
-
-2.10 Configure Options
- ==================
-
- Usage: configure [OPTIONS] [HOST]
-
- Where HOST and TARGET are something like "sparc-sunos", "mips-sgi-irix5",etc.
-
- `configure' recognizes the following options to control how it
- operates.
-
- NOTE: not all options are currently supported by this
- distribution. The following are the only ones supported.
-
- `--help'
- Print a summary of the options to `configure', and exit.
-
- `--prefix=MYDIR` install into MYDIR [$(toplevel)/NewHDF]
-
-
-3. Man pages
- =============
-
- Man pages can be found in:
-
- $(toplevel)/man
-
-4. Release notes
- =============
- The files in sub-directory $(toplevel)/release_notes are detailed
- descriptions for the new features and changes in this release.
- They can be used as supplemental documentation. These files are also
- available on the NCSA ftp server (ftp.ncsa.uiuc.edu) in:
-
- /HDF/HDF/HDF_Current/release_notes/.
-
-5. Documentation
- =============
-
- The HDF documentation can be found on the NCSA ftp server
- in the directory /HDF/HDF/Documentation/. The
- HDF home page is at:
-
- http://hdf.ncsa.uiuc.edu/
-
-6. FAQ
- ===
- An FAQ is available on our ftp server, as well as at:
- http://hdf.ncsa.uiuc.edu/HDF-FAQ.html
-
-
-7. HDF Java Products
- =================
- The HDF Java Interface and Java HDF Viewer are built
- separately after the library. See:
- http://hdf.ncsa.uiuc.edu/java-hdf-html/
-
-
-8. HELP
- ====
- If you have any questions or comments, or would like to be
- added to or removed from our hdfnews email list, contact us
- at:
-
- hdfhelp at ncsa.uiuc.edu
-
-
Added: packages/libhdf4/branches/upstream/current/INSTALL_WINDOWS.txt
===================================================================
--- packages/libhdf4/branches/upstream/current/INSTALL_WINDOWS.txt (rev 0)
+++ packages/libhdf4/branches/upstream/current/INSTALL_WINDOWS.txt 2007-05-15 09:53:05 UTC (rev 831)
@@ -0,0 +1,1159 @@
+ Installation Instructions for HDF4.2r1 on Windows 2000/XP
+========================================================================
+
+The instructions which follow assume that you will be using the HDF4
+source code archive from HDF website (http://hdf.ncsa.uiuc.edu).
+
+In building HDF4 from source code you may select between two build
+environment options ( with Fortran or without Fortran).
+
+***************************WARNINGS*************************************
+Please read CAREFULLY about the following preconditions first.
+
+Preconditions
+
+To build the HDF4 and MFHDF libraries ( single-threaded static or
+multi-threaded DLL) and utilities, it is assumed that you have done
+the following:
+
+ 1. Installed MicroSoft Visual Studio or Intel C compiler and WinZip.
+
+ 1.1 Installed DEC Visual Fortran compiler(6.0 or higher version)
+ or Intel Fortran compiler if you want to build the full HDF4
+ library with Fortran support.
+
+ 2. Set up a directory structure to unpack the source code archive.
+ For example:
+
+ c:\ (any drive)
+ MyHDFstuff\ (any folder name)
+
+ 3. Download the HDF4.2r1 source code archive HDF4.2r1.tar.gz from
+ ftp://ftp.ncsa.uiuc.edu/HDF/HDF/HDF_Current/src/ and use WinZip
+ to extract HDF4 source code into c:\MyHDFstuff. This creates a
+ directory called 'HDF4.2r1' under MyHDFstuff which contains
+ several files and directories. Rename "HDF4.2r1" to "HDF42r1".
+
+ 4. HDF4 provides options to do in-memory compress within HDF4
+ library. Currently, three external compression libraries ZLIB,
+ JPEG, and SZIP can be used with HDF4.
+
+ 4.1 HDF4 uses Zlib version 1.2.2 for compression. To use Zlib
+ library, you have to install your own Zlib DLL library or go
+ to ftp://hdf.ncsa.uiuc.edu/lib-external/zlib/bin/windows
+ to download the Zlib library.
+
+ Zlib compression feature inside HDF4 is required.
+
+ Note: Zlib 1.2.2 DLL library can also be downloaded from
+ http://www.zlib.net/zlib122-dll.zip
+
+ 4.2 HDF4 uses JPEG release 6b for compression. To use JPEG
+ library, you have to install your own JPEG library or go to
+ ftp://hdf.ncsa.uiuc.edu/lib-external/jpeg/bin to download
+ the JPEG library archive file jpeg-6b.exe.
+
+ JPEG compression feature inside HDF4 is required.
+
+ 4.3 HDF4 uses Szip version 2.0 for compression. To use Szip
+ library, you can download Szip source codes and binaries
+ from ftp://hdf.ncsa.uiuc.edu/szip/2.0/bin/windows/
+
+ Please note that Szip is not a totally open-source free
+ software. For licensing issue of Szip, please check
+ "Licensing terms" at
+ http://hdf.ncsa.uiuc.edu/doc_resource/SZIP/index.html.
+
+ Szip compression feature inside HDF4 is optional.
+
+ 5. Define the following environment variables:
+
+ HDF4_EXT_ZLIB
+ HDF4_EXT_JPEG
+ HDF4_EXT_SZIP
+
+ In this section, Szip compression software is assumed to be used.
+ Please read section VI as well as this section if you do not
+ want to use Szip compression feature inside HDF4.
+
+ To define these environment variables:
+
+ Click "Start", click "Control Panel", and then double-click
+ "System". On the "Advanced" tab, click "Environment Variables".
+
+ If you are logged on as administrator to the local computer AND
+ want to let all other users use these three environment variables,
+ click "New" under "System Variables" box; otherwise, click "New"
+ under "User Variables" box.
+
+ In the New Variable window, set "Variable name" as HDF4_EXT_ZLIB
+ and "Variable value" as zdll.lib, then click OK.
+
+ Similarly, you can set:
+
+ HDF4_EXT_JPEG environment variable as libjpeg.lib
+ HDF4_EXT_SZIP environment variable as szlibdll.lib
+
+ Notes:
+
+ a. You might have to close and reopen running programs for the
+ new environment variable settings to take effect.
+
+ b. c:\zlib122\zlib1.dll and c:\szlib\dll\szlibdll.dll should
+ be copied into the location that the application can find,
+ one suggestion is to use the c:\WINNT\system or
+ c:\WINDOWS\system
+
+ 6. Set up paths for external libraries and headers
+
+ Invoke Microsoft Visual C++ and go to "Tools" and select
+ "Options", find "Directories";
+
+ 6.1 Find the box "Show directories for", choose "Include files",
+ If you cannot find your Zlib, JPEG, and Szip header path
+ (for example, c:\zlib122\include, c:\jpeg-6b,
+ c:\szip\include) from the directory list, add the header
+ path (c:\zlib122\include, c:\jpeg-6b, c:\szip\include) to
+ the included directories.
+
+ 6.2 Find the box "Show directories for", choose "Library files",
+ If you cannot find your Zlib, JPEG, and Szip library path
+ (for example, c:\zlib122\lib, c:\jpeg-6b, c:\szip\dll)
+ from the directory list, add the library path
+ (c:\zlib122\lib, c:\jpeg-6b, c:\szip\dll) to the library
+ directories.
+
+************************************************************************
+
+The following sections discuss installation procedures in detail:
+
+ Section I: Build and Test HDF4 Libraries and Utilities
+ Section II: Build an Application Using the HDF4 Library
+ Section III: Build HDF4 in VS 7.0(.NET)
+ Section IV: Build HDF4 with Intel Compiler
+ Section V: Some Helpful Pointers
+ Section VI: Disable Szip Compression Feature inside HDF4
+ Section VII: Build and Test HDF4 Library on the Command Line
+ Section VIII: Build HDF4 Multithreaded Static Library
+
+************************************************************************
+
+
+Section I: Build and Test HDF4 Libraries and Utilities
+======================================================================
+
+Step 1: Select Installation Type
+
+You may select one of 2 ways to build the HDF4 libraries and utilities,
+depending on your environment and application needs.
+
+Option A, (select Win32.nofortran.zip)
+This is the "NOFORTRAN" configuration: it builds debug and release
+single-threaded and multi-threaded DLL versions of the HDF libraries,
+tests, and utilities. There is no Fortran support.
+
+Option B, (select Win32.zip)
+This is "WITH FORTRAN SUPPORT" configuration: it is the same as above
+but with Fortran support.
+
+
+Step 2: Build HDF4 Libraries and Utilities
+
+Notes:
+
+ a. The instructions are the same for both options A and B.
+
+ b. These instructions are written for MicroSoft Visual Studio 6.0
+ and DEC Visual Fortran users. For .NET users, please also read
+ section III. For Intel compiler users, please aslo read
+ section IV.
+
+ c. For Microsoft Visual C++ 6.0 and DEC Visual Fortran 6.0(or
+ higher versions) users, we support building HDF4 libraries and
+ utilities from the HDF4 source code archive on command line.
+ To build HDF4 on the command line, please read section VII.
+
+ d. To build HDF4 Multithreaded static library, please read
+ section VIII.
+
+Building Instructions:
+
+ 1. Unpack Win32.nofortran.zip or Win32.zip in directory HDF42r1\.
+
+ Note: Please select "Yes to All" when you are asked to confirm
+ file overwrite by WinZip.
+
+ 2. Invoke Microsoft Visual C++ 6.0, go to "File" and select the
+ "Open Workspace" option.
+
+ Then open the c:\MyHDFstuff\HDF42r1\all.dsw workspace.
+
+ 3. Select "Build", then Select "Set Active Configuration".
+
+ On Windows platform select as the active configuration
+
+ "all -- Win32 Debug" to build debug versions of
+ single-threaded static libraries, tests
+ and utilities and multi-threaded libraries
+ and tests.
+ or
+
+ "all -- Win32 Release" to build release versions of
+ single-threaded static libraries, tests
+ and utilities and multi-threaded
+ libraries and tests.
+
+ Select "Build" and "Build all.exe" to build the corresponding
+ version of the HDF42r1 library.
+
+ You should see 0 error at the end of building.
+
+ Warning messages can be ignored.
+
+ When the debug build is done the directories listed below will
+ contain the following files:
+
+ c:\MyHDFstuff\HDF42r1\windows\lib\debug\singlethreaded -
+
+ hd421d.lib - HDF static library
+ hm421d.lib - MFHDF static library
+
+ c:\MyHDFstuff\HDF42r1\windows\lib\debug\multithreaded -
+
+ hd421md.lib - HDF multi-threaded DLL export library
+ hm421md.lib - MFHDF multi-threaded DLL export library
+
+ c:\MyHDFstuff\HDF42r1\windows\dll\debug
+
+ hd421md.dll - HDF DLL
+ hm421md.dll - MFHDF DLL
+
+ c:\MyHDFstuff\HDF42r1\windows\bin\debug -
+
+ utilities, statically linked with the single-threaded
+ libraries.
+
+ When the release build is done the directories listed below will
+ contain the following files:
+
+ c:\MyHDFstuff\HDF42r1\windows\lib\release\singlethreaded -
+
+ hd421.lib - HDF static library
+ hm421.lib - MFHDF static library
+
+ c:\MyHDFstuff\HDF42r1\windows\lib\release\multithreaded -
+
+ hd421m.lib - HDF multi-threaded DLL export library
+ hm421m.lib - MFHDF multi-threaded DLL export library
+
+ c:\MyHDFstuff\HDF42r1\windows\dll\release
+
+ hd421m.dll - HDF DLL
+ hm421m.dll - MFHDF DLL
+
+ c:\MyHDFstuff\HDF42r1\Windows\bin\release -
+
+ utilities, statically linked with the single-threaded
+ libraries.
+
+Note: The ws2_32.lib needs to be linked with your executable if using
+ the static mfhdf library. The ws2_32.lib can be found in your
+ Microsoft Visual C++ directory under the lib folder.
+
+
+Step 3: Test HDF4 Libraries and Utilities
+
+HDF4 libraries and utilities should be tested to make sure that they
+were built correctly.
+
+We provide 2 options for users to test HDF4 libraries and utilities.
+
+ Option 1: Automatic testings
+
+ HDF4 comes with various test suites, all of which can be tested
+ with hdf4check.bat batch file in c:\MyHDFstuff\HDF42r1\ directory.
+
+ Invoke a command prompt window and run hdf4check.bat.
+
+ Test results are saved in:
+
+ c:\MyHDFstuff\HDF42r1\check_results.txt.
+
+ Use either Notepad or WordPad or whatever other windows word
+ processor to check the results. You should not find any FAILED
+ marks in check_results.txt.
+
+ Option 2: Step-by-step HDF4 libraries and utilities testings
+
+ You can also test debug and release versions of HDF4 libraries
+ and utilities separately.
+
+ DLLs listed below should be placed into the Windows system directory.
+ A batch file named install_dll.bat is included in
+ c:\MyHDFstuff\HDF42r1 directory. Run this batch file and the
+ following HDF4 DLLs will be copied to the system directory.
+
+ HDF42r1\windows\dll\release\hd421m.dll
+ HDF42r1\windows\dll\release\hm421m.dll
+ HDF42r1\windows\dll\debug\hd421md.dll
+ HDF42r1\windows\dll\debug\hm421md.dll
+
+ Then run Win32debugtst.bat to test debug version or
+ Win32releasetst.bat to test release version.
+
+ We strongly suggest you to redirect your testing results into an
+ output file so that you can easily check the testing results. You
+ may use either Notepad or WordPad or whatever other windows word
+ processor to check the results. You should not find any FAILED
+ marks in your output files.
+
+
+Step 4: ncgen -c test (Optional)
+
+ncgen is a netCDF utility that converts a CDL description of a netCDF
+file into an HDF file, or that generates the C or Fortran source
+code required to create a netCDF file.
+
+HDF4 includes "ncgen -c test" to test whether ncgen can generate the
+C source code required to create a netCDF file.
+
+Note:
+ Currently, ncgen can not generate the Fortran source code
+ required to create a netCDF file by HDF4 on Windows.
+
+ So "ncgen -f test" is not supported by HDF4 on Windows.
+
+ncgen project should have been built in step 2 before you can run
+"ncgen -c test" on Windows.
+
+Follow the instructions below to run "ncgen -c test" on Windows.
+
+ 1. Open all.dsw Workspace
+
+ Invoke Microsoft Visual C++ 6.0, go to "File" and select the
+ "Open Workspace" option.
+
+ Then open the c:\MyHDFstuff\HDF42r1\all.dsw workspace.
+
+ 2. Manually generate test0.c
+
+ A batch file named ctest0_gen.bat under c:\MyHDFstuff\HDF42r1\
+ directory is provided to create the C source code test0.c.
+
+ ctest0_gen.bat has 2 options:
+
+ ctest0_gen debug -- generate test0.c with debug ncgen
+
+ ctest0_gen release -- generate test0.c with release ncgen
+
+ Invoke a command prompt windows and run ctest0_gen.bat with
+ appropriate options, you should get test0.c under
+ c:\MyHDFstuff\HDF42r1\mfhdf directory.
+
+ Note: We suggest that users should use the test0.c generated by
+ debug version ncgen (by running ctest0_gen debug) to build
+ the debug version ctest0.exe.
+
+ Similarly, test0.c generated by release version ncgen (by
+ running ctest0_gen release) should be used to build the
+ release version ctest0.exe.
+
+ 3. Build ctest0.exe
+
+ Select "Build", then Select "Set Active Configuration".
+
+ On Windows platform select as the active configuration
+
+ "ctest0 -- Win32 Debug" to build debug versions ctest0
+
+ or
+
+ "ctest0 -- Win32 Release" to build release versions of ctest0
+
+
+ Select "Build ctest0.exe" to build the corresponding version of
+ ctest0.exe.
+
+ You should see 0 error at the end of building.
+
+ Warning messages can be ignored.
+
+ When the debug build is done the directories listed below will
+ contain the following files:
+
+ c:\MyHDFstuff\HDF42r1\windows\bin\debug
+
+ ctest0.exe - Debug version
+
+ c:\MyHDFstuff\HDF42r1\windows\bin\debug
+
+ ctest0.exe - Release version
+
+ 4. Run ncgen -c Test
+
+ A batch file named ncgen_ctest.bat under c:\MyHDFstuff\HDF42r1\
+ is provided to run "ncgen -c test".
+
+ ncgen_ctest.bat has 2 options:
+
+ ncgen_ctest debug -- debug version ncgen -c test
+
+ ncgen_ctest release -- release version ncgen -c test
+
+ Invoke a command prompt windows and run ncgen_ctest.bat with
+ appropriate options, you should get the following messages:
+
+ =========================
+ ncgen -c test
+ =========================
+ *** ncgen -c test successful ***
+
+
+Step 5: Install HDF4 Library
+
+We provide a batch file for users to relocate all HDF4 libraries in one
+folder. The file is called installhdf4lib.bat under
+c:\MyHDFstuff\HDF42r1 directory. Run the batch file, you may see a
+folder called hdf4lib under c:\MyHDFstuff\HDF42r1.
+
+The <release> layout of <hdf4lib> should be:
+
+ release\include -- HDF4 header files
+ release\bin -- HDF4 static utility executables
+ release\lib -- HDF4 static libraries
+ release\dll -- HDF4 multi-threaded libraries and DLLs
+
+You may also find the similar layout for the <debug>.
+
+
+Step 6: Building HDF4 C/Fortran examples (Optional)
+
+Simple examples have been provided for users to test HDF4 C/Fortran
+library and utilities.
+
+Note:
+ To build HDF4 Fortran examples, Win32.zip must have been
+ chosen in step 1.
+
+To build and test HDF4 C examples:
+
+ 1. Invoke Microsoft Visual Studio 6.0, go to "File" and select
+ the "Open Workspace" option.
+
+ Then open the workspace
+ c:\MyHDFstuff\HDF42r1\examples\allexamples\allexamples.dsw.
+
+ 2. Select "Build", then Select "Set Active Configuration".
+
+ In "Project configurations", select the active configuration
+
+ "allexamples -- Win32 Debug" to build debug versions of the
+ C examples.
+
+ or
+
+ "allexamples -- Win32 Release" to build release versions the
+ C examples.
+
+ When the debug build or release build is done, there should be the
+ following subdirectories in c:\MyHDFstuff\HDF42r1\examples\
+
+ chgnamtest
+ createtest
+ dimtest
+ gittest
+ rattrtest
+ readtest
+ sattrest
+ sds2grouptest
+ sh_dimtest
+ unltest
+
+ 3. Invoke a command prompt window and run the batch file
+ InstallExamples.bat which resides in the top level directory
+ (c:\MyHDFstuff\HDF42r1\). This file creates 2 new directories,
+ examplesREL and examplesDBG in the c:\MyHDFstuff\HDF42r1\examples
+ directory and places all the executables in it. Both the release
+ and debug versions of the examples should be built before this
+ step is done. The examples should be tested in these 2 new
+ directories due to some dependencies between the examples.
+ Especially createtest.exe should be executed before gitest.exe
+ and sattrtest.exe, and rattrtest should be executed immediately
+ after sattrtest.exe due to the dependencies among these files.
+
+
+To build and test HDF4 Fortran example:
+
+ 1. Invoke Compaq Visual Fortran or Intel Fortran under Microsoft
+ Visual Studio development environment, go to "File" and select
+ the "Open Workspace" option.
+
+ Then open the workspace
+ c:\MyHDFstuff\HDF42r1\fortran\examples\allf90examples\allf90examples.dsw.
+
+ 2. Select "Build", then Select "Set Active Configuration".
+
+ In "Project configurations", select the active configuration
+
+ "allf90examples -- Win32 Debug" to build debug versions of the
+ Fortran examples.
+
+ or
+
+ "allf90examples -- Win32 Release" to build release versions the
+ Fortran examples.
+
+ When the debug build or release build is done, there should be the
+ following subdirectories in c:\MyHDFstuff\HDF42r1\fortran\examples\
+
+ createtest
+ gittest
+ rattrtest
+ readtest
+ sattrest
+ sds2grouptest
+ sh_dimtest
+ unltest
+
+ 3. Invoke a command prompt window and run the batch file
+ Installf90Examples.bat which resides in the top level directory
+ (c:\MyHDFstuff\HDF42r1\). This file creates 2 new directories,
+ f90examplesREL and f90examplesDBG in the
+ c:\MyHDFstuff\HDF42r1\fortran\examples directory and places all
+ the executables in it. Both the release and debug versions of
+ the examples should be built before this step is done. The
+ examples should be tested in these 2 new directories due to
+ some dependencies between the examples. Especially createtest.exe
+ should be executed before gitest.exe and sattrtest.exe, and
+ rattrtest should be executed immediately after sattrtest.exe due
+ to the dependencies among these files.
+
+
+Note: Please read to Sections III and IV on how to build HDF4
+ C/Fortran examples with .NET and with Intel Compilers on .NET.
+
+
+Section II. Build an Application Using the HDF4 Library or DLLs
+======================================================================
+
+If you are building an application that uses the HDF4 library, the
+following locations will need to be specified for locating header files
+and linking in the HDF4 libraries:
+
+ <top-level HDF directory>\lib
+ <top-level HDF directory>\dll
+ <top-level HDF directory>\include
+
+where <top-level HDF directory> may be
+c:\MyHDFstuff\HDF42r1\hdf4lib\release or
+c:\MyHDFstuff\HDF42r1\hdf4lib\debug
+
+if you have installed HDF4 library in Section I, Step 5.
+
+We assume that you will use the Szip compression with HDF4 library.
+
+To specify these locations in the settings for your VC++ project with
+Microsoft Visual C++ 6.0:
+
+Under Tools->Options, select the folder, Directories:
+ Under "Show directories for", select "Include files".
+ Add the following directories:
+ c:<path to HDF includes>\include
+
+Under "Show directories for", select "Library files":
+ Add the following directories:
+ c:<path to HDF libs>\lib
+ c:<path to HDF libs>\dll
+
+Under Project->Settings, select folder, Link:
+ Add the following libraries to the beginning of the list of
+ Object/Library Modules:
+ hd421.lib hm421.lib (single-threaded release version)
+ hd421d.lib hm421d.lib (single-threaded debug version)
+
+ hd421m.lib hm421m.lib (multi-threaded release version)
+ hd421md.lib hm421md.lib (multi-threaded debug version)
+
+ HDF4_EXT_ZLIB
+ HDF4_EXT_JPEG
+ HDF4_EXT_SZIP
+
+Note: The above three environment variables should have been defined in
+ the preconditions. Paths for these external libraries and
+ headers should also have been set up in preconditions.
+
+ Follow the instructions in preconditions to define these three
+ environment variables and set up path for these external libraries
+ and headers if you can not find them.
+
+HDF4 DLLs should also be copied to the directory(for example,
+Windows system directory) where the application can find.
+
+Note: You can also follow the above instructions in this section if
+ want to build an application using the HDF42r1 binary
+ distributions available from
+ ftp://ftp.ncsa.uiuc.edu/HDF/HDF/HDF_Current/bin/windows.
+
+ Make sure to download appropriate binary distribution based on
+ your Windows platforms and compilers.
+
+ If you can not find the binary distribution matching with your
+ Windows platforms and compilers, you will have to build HDF4
+ libraries and utilities from the source codes.
+
+ Also, these binary distributions were pre-compiled with Szip
+ compression feature inside HDF4 library. If you do not want
+ to use the Szip compression feature, you will have to build HDF4
+ libraries and utilities from the source code following the
+ instructions in Section VI.
+
+
+Section III. Build HDF4 in VS 7.0(.NET)
+======================================================================
+
+In this section, we just briefly introduce some extra/different points
+when building HDF4 in VS 7.0(.NET). For other parts, you should still
+follow the instructions in Section I.
+
+1. Invoke MicroSoft Visual Studio .NET, go to "File" and select the
+"Open Solution" option. Choose "Compatible Workspace Files (*.dsw)"
+in the "Files of type:" text box and open the Visual Studio 6.0
+workspace c:\MyHDFstuff\HDF42r1\all.dsw.
+
+2. Select "Yes To All" when you are asked whether to convert and open
+project. .NET will automatically convert the workspace file to
+solution file.
+
+3. Find "Build" and go to "Configuration Manager"; choose
+"Release" or "Debug", then choose "Build all".
+
+4. If you want to change some project setting, select the project and
+right click the button to choose Properties; find the similar menu
+there as in 6.0.
+
+5. You need to specify the ZLIB, JPEG, and SZIP include header files
+and libraries under Tools->Options->Projects->VC++ Directories and
+choose Include and Libraries under the category of
+"show directories for" to add the corresponding path.
+
+6. To build HDF4 C examples on .NET, HDF4 C examples workspace files
+should be converted to solution files.
+
+Notes:
+
+ a. Currently we only build and test HDF4 with .NET on Windows XP.
+
+ b. To build HDF4 with Fortran support on .NET, Intel Fortran
+ compiler must also be installed in your computer. Please
+ read Section IV to build HDF4 with Fortran support on .NET.
+
+
+Section IV. Build HDF4 with Intel Compiler
+======================================================================
+
+Currently, HDF4 is supported with Intel compilers version 7.1 and
+version 8.1 on .NET.
+
+In this section, we just briefly introduce some extra/different points
+when building HDF4 with Inel compiler 7.1 or 8.1 on .NET. For other
+parts, you should still follow the instructions in Sections I and IIV.
+
+To use Intel compilers, all HDF4 workspace files must be converted
+to solution files as instructed in Section III.
+
+Part 1. Intel 7.1 Compiler
+
+For Intel 7.1 compiler users, Intel compiler should be selected before
+building HDF4 library and utilities. Follow the instructions below to
+select Intel C/Fortran compilers.
+
+1. Intel 7.1 C Compiler
+ Go to Tools-->Select Compiler
+ Check Intel box and click OK button
+
+2. Intel 7.1 Fortran Compiler
+ Go to Tools-->Select Compiler
+ Check Intel box and click OK button
+ Go to Tools-->Customize-->Add-ins and Macro Files
+ and check Intel Fortran Compiler Build Tool
+
+Part 2. Intel 8.1 Compiler
+
+Preconditions:
+
+a. Set up paths for Intel 8.1 libraries and DLLS
+
+ c:\Program Files\Intel\CPP\Compiler80\Is32\LIB and
+ c:\Program Files\Intel\FORTRAN\Compiler80\Is32\LIB should
+ be added into environment variable "PATH" so applications
+ can find Intel 8.1 libraries and DLLs.
+
+b. Set up external libraries and headers paths for Intel 8.1
+ Fortran compiler (only required if you want to use Intel
+ 8.1 Fortran compiler)
+
+ Invoke Microsoft Visual Studio .NET and go to Tools-->Options,
+ select "Intel(R) Fortran";
+
+ 1) Go to "Project Directories" and choose "Includes:",
+ If you cannot find your Zlib, JPEG, and Szip header paths
+ (for example, c:\zlib122\include, c:\jpeg-6b, c:\szip\include)
+ from the directory list, add the header path (c:\zlib122\include,
+ c:\jpeg-6b, c:\szip\include) to the included directories.
+
+ 2) Go to "Project Directories" and choose "Libraries:",
+ If you cannot find your Zlib, JPEG, and Szip library paths
+ (for example, c:\zlib122\lib, c:\jpeg-6b, c:\szip\dll)
+ from the directory list, add the library path (c:\zlib122\lib,
+ c:\jpeg-6b, c:\szip\dll) to the library directories.
+
+
+1. Build HDF4 without Fortran support
+
+ To build HDF4 without Fortran support with Intel 8.1 C++ compiler,
+ HDF4 solution files must be converted to use Intel(R) C++ project
+ system.
+
+ To make the conversion, choose all the project files in solution
+ "all" except the "all" dummy project (totally 49 projects)
+ Go to Project-->Convert to use Intel(R) C++ Project System
+
+ After the converion, HDF4 without Fortran support can be built
+ and tested following instrctions in Sections I and III.
+
+ Notes:
+
+ a. The "all" dummy project could not be converted to use
+ Intel(R) C++ project system, which will not affect
+ building HDF4 with Intel compilers.
+
+ b. When building "test" and "util" projects, you will get a
+ link error:
+
+ LINK : error LNK2001: unresolved external symbol _WinMainCRTStartup
+
+ This error message can be ignored. "test.exe" and
+ "util.exe" are never created, so it is OK.
+
+ c. You need to unpack Win32.nofortran.zip in directory HDF42r1\ again
+ if you rebuild or clean any project as Intel compiler will
+ delete all *.bat and *.out files during the cleaning process.
+
+ d. HDF4 C examples should also be converted to use Intel(R) C++
+ project system if HDF4 C libraries are built with Intel 8.1
+ compiler.
+
+
+2. Build HDF4 with Fortran support
+
+ To build HDF4 with Fortran support with Intel 8.1 C++/Fortran
+ compilers, HDF4 sulution files must be converted to use Intel(R)
+ C++/Fortran project system.
+
+ 1) Extract Compaq Visual Fortran Projects Items from the
+ following 8 projects:
+
+ dllfortestf
+ dllhdftestf
+ fortestf
+ hdf
+ hdf_dll
+ hdftestf
+ mfhdf
+ mfhdf_dll
+
+ To make the extraction, right click appropriate projects and
+ select Extract Compaq Visual Fortran Projects Items on the
+ right-click menu.
+
+
+ Notes:
+
+ a. Above projects should not be converted into Intel(R) C++
+ project system. Otherwise, you could not extract Fortran
+ projects items from converted Intel(R) C++ projects
+ anymore and Fortran source codes in those projects will
+ not be compiled.
+
+ b. As dllfortestf, fortestf, hdf, hdf_dll, mfhdf, and
+ mfhdf_dll projects contains both Fortran and C/C++
+ project files. The Intel(R) Fortran project converter
+ will split each of the above project into 2 Visual Studio
+ projects - a Visual C++ project and an Intel(R) Fortran
+ project.
+
+ Please choose the Intel(R) Fortran project as the main
+ project before splitting.
+
+ Meanwhile, the following projects will be created by the
+ Intel(R) Fortran project converter after the splitting:
+
+ dllfortestf_lib
+ fortestf_lib
+ hdf_dll_lib
+ hdf_lib
+ mfhdf_dll_lib
+ mfhdf_lib
+
+ 2) Convert the rest projects (including the six projects created
+ in the above step and except the "all" dummy project) into
+ Intel(R) C++ project system.
+
+ 3) Right clik project "hdf", go to Properties,
+ in the "Configuration:" text box, select "Debug",
+ go to Librarian-->Output Files, rename the output from
+ $(OutDir)/$(ProjectName).lib to
+ $(OutDir)/$(ProjectName)d.lib, then press "OK".
+
+ 4) Right clik project "mfhdf", go to Properties,
+ in the "Configuration:" text box, select "Debug",
+ go to Librarian-->Output Files, rename the output from
+ $(OutDir)/$(ProjectName).lib to
+ $(OutDir)/$(ProjectName)d.lib, then press "OK".
+
+ 5) Right clik project "hdf_dll", go to Properties,
+ in the "Configuration:" text box, select "Release",
+ go to Linker-->Advanced, rename the "Import Library" from
+ $(OutDir)/hdf_dll.lib to $(OutDir)/hd421m.lib,
+ then press "OK".
+
+ 6) Right clik project "mfhdf_dll", go to Properties,
+ in the "Configuration:" text box, select "Release",
+ go to Linker-->Advanced, rename the "Import Library" from
+ $(OutDir)/mfhdf_dll.lib to $(OutDir)/hm421m.lib,
+ then press "OK".
+
+ After the above converion and modifications, HDF4 with Fortran
+ support can be built and tested following instrctions in
+ Sections I and III.
+
+ Notes:
+
+ a. "dlltesthdf" project can not be built with Intel 8.1 Fortran
+ compiler. Please ignore this failure.
+
+ b. The "all" dummy project could not be converted to use
+ Intel(R) C++ project system, which will not affect
+ building HDF4 with Intel compilers.
+
+ c. When building "test" and "util" projects, you will get a
+ link error:
+
+ LINK : error LNK2001: unresolved external symbol _WinMainCRTStartup
+
+ This error message can be ignored. "test.exe" and
+ "util.exe" are never created, so it is OK.
+
+ d. You need to unpack Win32.zip in directory HDF42r1\ again
+ if you rebuild or clean any project as Intel compiler will
+ delete all *.bat and *.out files during the cleaning process.
+
+ e. HDF4 C examples should also be converted t use Intel(R) C++
+ project system if HDF4 C libraries are built with Intel 8.1
+ compiler.
+
+ f. You should extract Compaq Visual Fortran Project Items from
+ HDF4 Fortran examples if HDF4 Fortran libraries are built with
+ Intel 8.1 compiler.
+
+ g. For all HDF4 Fortran examples projects, right click
+ Properties, in "Configuration:" text box, choose "Debug",
+ Go to Linker-->Input-->Additional Dependencies,
+ replace hm421d.lib and hd421d.lib with hdfd.lib and mfhdfd.lib.
+
+ h. For all HDF4 Fortran examples projects, right click
+ Properties, in "Configuration:" text box, choose "Release",
+ Go to Linker-->Input-->Additional Dependencies,
+ replace hm421.lib and hd421.lib with hdf.lib and mfhdf.lib.
+
+ i. To use HDF4 fortran libraries built with Intel 8.1 compiler,
+ c:\MyHDFstuff\HDF42r1\windows\lib\release\singlethreaded\hdf.lib
+ c:\MyHDFstuff\HDF42r1\windows\lib\release\singlethreaded\mfhdf.lib
+ c:\MyHDFstuff\HDF42r1\windows\lib\debug\singlethreaded\hdfd.lib
+ c:\MyHDFstuff\HDF42r1\windows\lib\debug\singlethreaded\mfhdfd.lib
+ should also be installed to appropriate directories.
+
+
+Section V: Some Helpful Pointers
+======================================================================
+
+(as described in terms of installing the nofortran configuration)
+
+Here are some notes that may be of help if you are not familiar
+with using the Visual C++ Development Environment.
+
+Project name and location issues:
+
+ The files in Win32.zip and Win32.nofortran.zip must end up in the
+ HDF42r1\ directory installed by HDF4.2r1.tar.gz.
+
+ If you must install all.dsw and all.dsp in another directory,
+ relative to HDF42r1\ , you will be asked to locate all sub-project
+ files, when you open the project all.dsw.
+
+ If you want to rename all (the entire project), you will need to
+ modify two files all.dsw and all.dsp as text (contrary to the
+ explicit warnings in the files).
+
+ You can also modify all.dsw and all.dsp as text, to allow these 2
+ files to be installed in another directory.
+
+Settings... details:
+ If you create your own project, the necessary settings can be
+ read from the all.dsp file(as text), or from the Project Settings
+ in the Developer Studio project settings dialog.
+
+
+