| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Description:
It seems that during the conversion, one project (h52gifdll) began using the wrong Runtime-library settings. This was causing Link errors for only the Release DLL build. This has been fixed now.
Tested:
VS.NET on WinXP
|
|
|
|
|
| |
Description:
Updated level of support for MinGW, Windows XP x64 and Windows Vista. Also noted that VS6 is no longer supported.
|
|
|
|
|
| |
Description:
After doing a quick review of the documentation, I found a few points that had been overlooked before.
|
|
|
|
|
| |
Description:
In the Windows command line build script, there was a reference to the "typegen" project, which generates h5detect before HDF5 is built. Now, we integrate h5detect into the overall build process, and typegen has been removed. This checkin removes the reference in the batch script. This fixes bugzilla bug 1021.
|
|
|
|
|
| |
Details:
We no longer support Visual Studio 6.0, so we note it in the documentation. Also, updated the path references in VS.NET documentation
|
|
|
|
|
|
|
|
| |
Description:
Minor edit to MANIFEST, delete a few entries I missed last time. This brings it up to date.
Tested:
chkmanifest on smirom
|
|
|
|
|
| |
Description:
We no longer have support for Fortran in VS.NET, so we remove references to any Fortran projects.
|
|
|
|
|
| |
Description:
Update the MANIFEST for the files I've just addeed/removed.
|
|
|
|
|
| |
Description:
We are removing VS6 support in HDF5 1.8, so our windows_vs6 folder now becomes windows_vnet.
|
|
|
|
|
| |
Description:
This is the first step in a series of commits that will remove VS6 support. In doing so, we'll need to convert our projects to VS.NET format, to maintain VS.NET C support. In this commit, I've converted all VS6 projects, and removed any Fortran remnants. I haven't updated the MANIFEST because I have a few more add/deletes, but I'll do that soon.
|
|
|
|
|
|
|
|
| |
Description:
There were a number of updates to the main h5dump test script. This checkin brings those edits to the Windows script as well.
Tested:
VS2005 w/ WinXP
|
|
|
|
|
|
|
| |
Correct typo in C++ example program
Tested on:
Mac OS X/32 10.5.1 (amazon)
|
|
|
|
|
|
|
| |
Clean up thread safety code a bit more...
Tested on:
Mac OS X/32 10.5.1 (amazon) w/threadsafe
|
|
|
|
|
|
|
| |
Minor cleanups and clarifications to prototype information.
Tested on:
Mac OS X/32 10.5.1 (amazon)
|
|
|
|
|
|
|
|
| |
Correct the prototype for H5Sselect_elements() to take an 'hsize_t *' for
the coordinates, instead of 'hsize_t **'.
Tested on:
Mac OS X/32 10.5.1 (amazon)
|
|
|
|
|
|
|
|
| |
Streamline threadsafety code to be simpler and reduce latency of holding
locks.
Tested on:
Mac OS X/32 10.5.1 (amazon) w/threadsafe
|
|
|
|
|
|
|
|
| |
Handled truncated files better, when the truncation falls in decoding a
local heap.
Tested on:
Mac OS X/32 10.5.1 (amazon)
|
|
|
|
|
|
|
|
| |
Description:
This catches up Windows to most of the new source files that have been added. Specifically, H5FDpkg.h and H5FDspace.c have been added to the library projects, and tcoords.c has been added to testhdf5. This goes for VS2005 and VS6 project files.
Tested:
Only built, VS2005
|
|
|
|
|
|
| |
Tested: kagiso only. Not need for h5committest since it is a configure simple
change. If it works correct in kagiso, it should work the same for all other
machines.
|
|
|
|
|
|
| |
bug with size > 1
tested: linux
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change H5P[gs]et_format_bounds() => H5P[gs]et_libver_bounds() and also
enumerated values H5F_FORMAT_{EARLIEST, LATEST} => H5F_LIBVER_{EARLIEST, LATEST}
Tested on:
FreeBSD/32 6.2 (duty) in debug mode
FreeBSD/64 6.2 (liberty) w/C++ & FORTRAN, in debug mode
Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe,
in debug mode
Linux/64-amd64 2.6 (smirom) w/default API=1.6.x, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
w/szip filter, in production mode
Mac OS X/32 10.4.10 (amazon) in debug mode
Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
|
|
|
|
|
|
| |
modified the 3D test case for subsetting with block and stride factors
tested: windows, linux
|
|
|
|
|
|
|
| |
modified the 2D test case for subsetting with block and stride factors
tested: windows, linux
|
| |
|
|
|
|
|
|
| |
modified the 1D test case for subsetting with block and stride factors
tested: windows, linux
|
|
|
|
|
|
|
| |
more progress on the block hyperslab bug, clean code
tested: windows, linux
|
|
|
|
| |
tested: windows, linux
|
|
|
|
|
| |
not tested, since /examples has several compiling errors due to new APIs
this check in should have no problems
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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:
FreeBSD/32 6.2 (duty) in debug mode
FreeBSD/64 6.2 (liberty) w/C++ & FORTRAN, in debug mode
Linux/32 2.6 (kagiso) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe,
in debug mode
Linux/64-amd64 2.6 (smirom) w/default API=1.6.x, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Solaris/32 2.10 (linew) w/deprecated symbols disabled, w/C++ & FORTRAN,
w/szip filter, in production mode
Mac OS X/32 10.4.10 (amazon) in debug mode
Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
|
| |
|
| |
|
|
|
|
| |
tested: windows, linux
|
|
|
|
|
|
| |
we will need to rename tar ball for the
VMS user; used generic name <source> to specify the tar ball and top directory names for now.
|
| |
|
|
|
|
|
|
|
|
| |
annoying warning messages
and to delete temporary files
Platforms tested: VMS server
|
|
|
|
| |
Tested on smirom.
|
|
|
|
|
|
|
|
|
| |
Updated utilities test scripts to make output more legible; fixed some typos.
Added four new expected output files to avoid false negative reports
for the h5dump tests (for ones that expect to have error report in them).
Updated MANIFEST to reflect the changes.
Platforms tested:
VMS server (more testing is on the way)
|
|
|
|
|
|
|
|
| |
H5Sselect_hyperslab for test
purpose.
Tested on smirom only. Simple changes.
|
|
|
|
|
|
|
|
| |
calculation of dataspace selection.
It covers many cases.
Tested on smirom, kagiso, and linew.
|
| |
|
| |
|
|
|
|
|
|
| |
note: RFC at http://www.hdfgroup.uiuc.edu/RFC/HDF5/NaNs_and_HDF5/
tested: windows, linux, solaris
|
| |
|
|
|
|
| |
tested: windows, linux
|
|
|
|
|
|
|
|
| |
on the h5repack verify function
note: some sybols were made public
tested: windows, linux
|
|
|
|
|
|
| |
false negative tests.
Platforms tested: VMS server
|
|
|
|
|
|
| |
modified h5import test script to cleanup the files after the test;
modified "master" building script to run tools tests.
Platforms tested: VMS server (not quite done yet)
|
|
|
|
|
|
| |
needed by h5repack
tested: windows, linux
|
| |
|
|
|
|
|
|
|
|
|
| |
Updates from running bin/reconfigure on recent changes, in preparation for
making private snapshot. Also updated tracing information for recent types
added to public API routines.
Tested on:
Linux/32 2.6.x (kagiso)
|