| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Removed legacy Visual Studio solutions and projects, which will
no longer be supported after HDF5 1.8.10.
|
| |
|
|
|
|
| |
Runtime library setting should be to DLL versions for static.
Tested: windows
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Tested: windows
|
| |
|
|
|
|
| |
Changed batch files by removing VS2005 and IVF91 options.
Added libsettings project to behave like h5tinit.vcproj.
Updated Manifest
|
| |
|
|
| |
files
|
| |
|
|
|
|
|
|
|
|
|
|
| |
h5repack test
Description:
The test script format was changed for h5import, including many file-name changes. This checkin brings those updates to Windows.
This checkin also disables a previously-added h5repack test for the userblock. The test is disabled for now because Windows cannot find the input file ublock.bin. The file is generated dynamically on other systems, but cannot be easily generated for use on Windows. We should re-enable this test in the future when ublock.bin is added to svn.
Tested:
VS2005 on WinXP
|
| |
|
|
|
|
|
|
|
|
| |
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:
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
|
| |
|
|
|
|
|
|
|
| |
Description:
Purpose: Fix very minor typo in Windows h5import test script
Single-letter typo in the Windows test script was causing us to return the wrong error code in some cases.
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 h5import tools project file.
Solution:
Platforms tested:
MSVS 6.0 on windows xp.
Misc. update:
|
