| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Added c++/test/tlinks.cpp
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Embed the content of libhdf5.settings into the hdf5 executables so that an
"orphaned" executables can display (via the Unix strings command, for example)
the library settings used to build the executables.
configure.in:
Added the --disable-embedded-libinfo option to disable this feature.
configure:
src/H5config.h.in:
fortran/configure
c++/configure
Generated by autotools like automake.
src/H5detect.c:
Implement insert_libhdf5_settings() to insert the contents of
libhdf5.settings into the library as an extern string variable so that it
is included in all HDF5 executable.
test/Makefile.in:
Added test scripts testlibinfo.sh and testcheck_version.sh, test program
tcheck_version. Needed to introduce $PROGS so that tcheck_version is
built but not run automatically.
test/testlibinfo.sh.in:
A new test added to verify the library information is indeed included
in the executables.
H5.c: added code to print the embedded library information when there is
a library versions mis-match occurs. This ensures the library information
string is included in the executable.
Also modifies the code so that the Library mismatch warning string is
included only once in the executable.
H5private.h:
Added a global reference to the libinfo string variable to prepare
for possible stage 3 implementation of a public API.
New test: (Bug ID 1656):
Add new tests (tcheck_version, testcheck_version.sh) to verify H5check_version()
does issue warnings and abort accordingly.
Changed H5check_version() to suppress the warning message totally if
$HDF5_DISABLE_VERSION_CHECK is 2 or higher. (Old behavior treated 3 or higher
the same as 1, that is to print a warning and allows the program to continue.
MANIFEST:
updated with the newly added files.
Tested:
h5committest passed. Also passed jam in serial mode, --enable-static-exec,
--disable-embedded-libinfo.
|
|
|
|
|
|
|
|
|
|
|
| |
Add backward compatibility test to make certain that the 1.6 library
handles encountering a file with a fixed array chunk index gracefully.
Also, remove the (generated) testh5ls.sh at 'make distclean'
Tested on:
FreeBSD/32 6.3 (duty) w/production
(too minor to require h5committest)
|
|
|
|
|
|
|
| |
Add new PDF files:
./doc/html/PSandPDF/HDF5_UG_r166.pdf
./doc/html/PSandPDF/HDF5_RM_r166.pdf
Tested: chkmanifest
|
|
|
|
| |
Tested by bin/chkmanifest.
|
|
|
|
|
| |
Remove old version of "HDF5 Tutorial" from doc repositories;
this document is maintained idependently.
|
|
|
|
|
|
| |
family_v1.8_0000[0-3].h5 from last round commit.
No test needed.
|
|
|
|
|
|
|
| |
big or little endian machine. Configure.in was modified to export a variable carrying endianess information to testh5ls.sh. This script then compares the current run with 2 expected outputs, one for a big-endian machine (linew was used to generate the output), other for little endian (jam was used to generate the output)
the way h5ls prints types, it starts searching for NATIVE types first. One solution would be h5ls not to detect these native types, using for example the same print datatype function that h5dump does, that would make the output look the same on all platforms ("32-bit little-endian integer" would be printed instead). Drawback, this "native" information would not be available. Other solution is to have not one but 2 expected outputs and make the shell script detect the endianess and compare with one output or other
tested: h5committest
|
|
|
|
|
|
|
|
| |
Implemented RFC. The new option is <-c, --compare List objects that are not comparable>
added some test cases and new test files for output
tested: h5committest
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reference Manual Breakout
Description:
Pulled functions out of reference manual .html files into individual
files per function, sorted into subdirectories. The files are included
into index files via php redirects, so the browser presentation of the
information has not changed, but maintenance on said files should
prove to be a bit easier.
|
|
|
|
|
|
|
|
|
| |
Storage: information not available
When displaying storage information for VL and dataset region types
Added 2 shell runs that display this information
#818
Tested: windows, linux
|
|
|
|
|
|
|
| |
The information of libhdf5_fortran.settings are all included in
libhdf5.settings now. Remove it from the source.
Tested: kagiso with fortran and C++.
|
|
|
|
| |
tested: linux
|
|
|
|
| |
tested: linux
|
|
|
|
|
|
| |
return 2 instead of -1 on error status
Tested: windows, linux
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The TEXTFPE was described in the usage (read floats in scientific notation) but was not implemeneted.
Solution:
remove TEXTFPE from the help system and have the TEXTFPE input type do
the same thing as TEXTPF currently does to support backwards compatibility (the format read for both TEXTFPE and TEXTPF is %f)
added a test
tested: windows, linux, solaris
|
|
|
|
| |
windows shell script only Note: for the unix shell script this file is not used
|
|
|
|
|
|
|
|
| |
HDF5 library. The Dependencies files are generated by
"make depend".
Tested:
h5committest, also serial in Kagiso is tested.
|
|
|
|
| |
Tested on kagiso, cobalt, and abe.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bug fixes.
Description:
Added code to create an empty hdf5 (named h5diff_empty.h5) in order to test
if h5diff compares correctly an empty hdf5 vs. a non-empty one.
Tested:
Tested in kagiso of h5diffgentest itself.
Verified by h5dump that h5diff_empty.h5 was indeed empty.
Then "h5diff h5diff_empty.h5 h5diff_basic1.h5" returned 0 (should have
returned non-zero).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a test for the floating point user defined printf format
Usage is
-m T, --format=T
Where T - is a string containing the floating point format, e.g '%.3f'
The test consists of writing a number with 7 fractional digits (default precision display of %f is 6 digits) and have the 7 digits displayed with
-m %.7f fpformat.h5
Tested: windows, linux, solaris
Note: the output file was generated in linux, it may be possible that platforms other than the ones tested have a different representation of the number
|
|
|
|
|
|
|
| |
h5dump bug fix
- Fixed h5dump regarding the display of array indices and block selections in
subsetting. PVN 2008/03/10
|
|
|
|
|
|
|
|
| |
Description:
Removed ./c++/examples/testexamples.sh
Platforms tested:
Not needed.
|
|
|
|
|
|
|
| |
non-repeat
test.
Updated MANIFEST for this new file.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
just use one of them and remove the other from svn
tested: linux, solaris
|
|
|
|
|
|
|
|
|
|
| |
generated by h5importtest on each test run,
others were in svn and used from that location (don't know why the difference)
per windows developer (SW) request made all the used text input files to be in svn
the binary files are obviously dynamically generated by h5importtest on each run
tested: linux, solaris
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
text input files = .txt
binary input files = .bin
configuration files = .conf
hdf5 files = .h5
besides that in very test the files have the same name except extension.
For example
TOOLTEST txtin16.txt -c $srcdir/testfiles/txtin16.conf -o txtin16.h5
The convention for the test name is for example, for "txtin16"
"txt" for text then "in16" means integer 16 size
Tested: linux, solaris
|
| |
|
|
|
|
|
|
| |
fread in windows needs a binary file to be open with "rb" instead of "r" otherwise it terminates execution if an end of file character is found on the input file. Besides that the binary file generated needs to be open with "wb" , otherwise an end of line character is read twice. FOR 1.6 ONLY (To do for 1.8)
tested: windows, linux, solaris
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add work-around to allow reading files that were produced with a buggy
earlier version of the library, which could create objects with the wrong
object header message count. There is now a configure flag
"--enable-strict-format-checks" which triggers a failure on reading a file
with this sort of corruption (when enabled) and allows the object to be read
(when disabled). The default value for the "strict-format-checks" flag is
yes when the "debug" flag is enabled and no when the "debug" flag is disabled.
Note that if strict format checks are disabled (allowing objects with
this particular kind of corruption to be read) and the file is opened with
write access, the library will re-write the object header for the corrupt
object with the correct # of object header messages.
This closes bugzilla bug #1010.
Tested on:
Linux/32 2.6 (kagiso)
FreeBSD/64 6.2 (liberty)
|
| |
|
|
|
|
| |
Fixed it.
|
|
|
|
|
|
|
| |
Removed the stream-vfd from the basic library code.
Platforms tested:
Kagiso (serial and parallel).
|
| |
|
|
|
|
| |
PDF-generating process.
|
|
|
|
|
|
|
|
| |
Description:
Made simple changes to Windows documentation, mostly correcting supported compilers.
Tested:
chkmanifest
|
|
|
|
| |
Tested with bin/chkmanifest
|
|
|
|
| |
files have been removed
|
|
|
|
| |
i686-darwin8.8.2 to i686-apple
|
|
|
|
|
|
|
|
|
| |
Removing release_docs/INSTALL_codewarrior.txt as Code Warrior is
not supported in this release.
Testing:
Visual inspection.
The removed file is a release_docs/ text file and
the change in MANIFEST is the removal of that filename.
|
|
|
|
| |
and updated MANIFEST
|
|
|
|
|
|
| |
remove a file that does not need to be in svn, since it is generated in the h5repack test program
tested: linux
|
| |
|
| |
|
|
|
|
| |
new file for the h5dump binary test, h5import configuration file
|