| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Tested: windows
|
|
|
|
|
|
| |
Changed batch files by removing VS2005 and IVF91 options.
Added libsettings project to behave like h5tinit.vcproj.
Updated Manifest
|
|
|
|
| |
files
|
|
|
|
| |
added missing display buffer resize test.
|
|
|
|
|
|
|
|
| |
Description:
The h5dump test script was recently updated to add the new -b syntax. This update also adds and modifies the neccessary tests for Windows.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
| |
Description:
This checkin includes updates to Windows test scripts for h5copy, h5diff, and h5dump tools. Each represents minor changes to syntax which emulates the updates made to the general-platform test scripts.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
|
| |
Description: Improved external link traversal of h5dump. h5dump will now
properly avoid all cycles, even those spanning multiple files. Improvement
to the output of committed datatypes. Committed datatypes are now checked
for uniqueness (like other objects). Tests added for these cases.
Tested: kagiso, linew, smirom (h5committest)
|
|
|
|
|
|
|
|
|
|
| |
Studio 2005
Description:
On Windows, we receive many compiler warnings because Microsoft has implemented many "security-enhanced" versions of POSIX functions. However, the old versions still exist, so the warnings can be ignored. By setting a preprocessor definition, we can disable many of these warnings. On a typical HDF5 build, this reduces the number of warnings from ~1500 to ~600
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ignored system library, standardize program debug information, and unify Windows h5tinit
Description:
These changes are made via a user's suggestion, bugzilla bug #1164. These have all been tested in the trunk, and are stable/favorable changes.
In many of our project files on Windows, we have our linker setting set to ignore old link libraries-- either libc.lib or libcd.lib. This is a relic from converting project files from old versions of Visual Studio to newer ones, and is unnecessary. We remove the ignored library from the project files. This actually makes no difference in the output binaries.
In our debug project configurations, many of the projects were generating debug information for "Program Database and Edit & Continue". Other projects were using different settings, or none at all. We standardize to use "Program Database" setting, because it generates much smaller .obj files and cuts out unnecessary debug information.
Previously, there was Windows-dependent code inside H5detect.c, because not all projects could access the gethostname() function. However, we standardize our project-files to link with WS2_32.lib, so now this function is available. Thus, the Windows-specific code has been removed from H5detect.c.
Tested:
VS2005 on WinXP
VS.NET on WinXP
|
|
|
|
|
|
|
|
| |
Description:
Shortly before the release, we noticed that one of our h5dump xml Windows tests failed when used with a release tarball. This is because of the Unix-style EOL characters in the expected output. For the release, we simply skipped the test. However, we can instead convert the expected output to Windows EOL format, and run the test. This is a backport from the HDF5 trunk.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
| |
Description:
On test fails from the release tarball. Specifically, the h5diff xml test for tsaf.h5.xml. For some reason, fc (Windows diff utility) detects differences from the expected output if the file has unix-style end-of-line characters. It only happens for this test. I suspect it is because the file is so long, but it's too late to debug for the release. Simply comment it out until we can fix it.
Tested:
VS2005 on WinXP (32- and 64-bit)
|
|
|
|
|
|
|
|
| |
Description:
One test has been added to h5dump test for custom output formats. This adds the test on Windows as well.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
In previous versions of Windows, the builtin 'FC' command (diff equivalent) didn't return proper exit status. As a work-around, we parsed the message returned to check status. This relies on English return messages.
In current Windows XP and Windows Vista, FC will return exit status as expected, so we can remove this workaround. Older platforms where we would need this workaround are no longer supported.
Tested:
VS2005 on Windows XP
Small test on Windows Vista
|
|
|
|
|
|
|
|
|
|
| |
Windows h5dump test script
Description:
There was another update to the main h5dump test script. This checkin brings those edits to the Windows script as well.
Tested:
VS2005 w/ WinXP
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
Description:
-- Add new source files to Windows projects: H5Pdeprec.c, H5Pint.c, H5Ddbg.c, H5Dint.c
-- Add new h5dump XML tests to Windows test script
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
| |
Description: Add 4 new tests to the Windows h5dump test script. See rev. 14182 and 14188 for details.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
| |
Description:
A few more tests were added to the Linux h5dump test script-- this brings Windows up-to-date.
Tested:
VS2005 on WinXP
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
64-bit Fortran
Description:
This checkin is another Windows project cleanup, and also extends our Windows support for 64-bit Fortran. Project files are now in VS2005 format, rather than VS.NET. A couple projects have been renamed to be more descriptive (*cstub rather than *_lib), and project settings make better use of build macros. This will make them much easier to update in the future.
Tested:
VS2005 on WinXP 32-bit
VS2005 on WinXP x64
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
We are porting Fortran to 64-bit Windows, and need to make many syntactical changes to bring the code up to date. We now go back to using "!DEC$" rather than "!MS$" in our "ATTRIBUTE" code. Also, the naming conventions for mixed language is inconsistent from 32- to 64- bit Windows. To make up with this, we use the "decorate" flag. We also needed to change the "calling convention" in project settings from "CVF" to "default".
Also other minor cleanups on project files.
Tested:
32-bit: VS.NET and VS2005
64-bit: VS2005
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Desciption:
This is the first major check-in in the process of depreciating Visual Studio 6.0. We create a new directory, windows_vs6, which now holds all of our previous VS6 project files. We expect to maintain this directory for only a short time (perhaps one release), so users have time to make the change.
The ./windows directory now contains project files for Visual Studio .Net, as well as existing source and test scripts. This will allow us to greatly simplify the build process for the majority of our users.
We have created a new solution (.Net equivolent of workspace) that houses the Fortran project files. This allowed us to remove these files from the main solution, as well as streamline the conversion in the Fortran solution. It is also much easier now to convert to Visual Studio 2005 files.
Notes:
I didn't update the MANIFEST with this check-in, I will make those changes shortly.
Also, I haven't yet updated the documentation to reflect this check-in. That is going to require more work.
We will be giving a seminar in the coming weeks about .Net and how to migrate over.
Tested:
VS6/VNET/VS2005 on WinXP 32/64-bit
|
|
|
|
|
|
| |
be "CRLF"
instead of "native".
|
|
For windows support, remove all.zip from hdf5.
Description:
Add h5dump tools project file.
Solution:
Platforms tested:
MSVS 6.0 on windows xp.
Misc. update:
|