| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Description:
Two new files, h5rdeprec.c and h5rpkg.h were added to the Windows HDF5 projects.
Tested:
VS2005, build only.
|
|
|
|
|
|
|
|
| |
Description:
In my large checkin yesterday, I forgot to add a few Windows project files that were renamed. This should bring the MANIFEST up to date.
Tested:
Will use chkmanifest after commit
|
|
|
|
|
|
|
|
| |
Description:
There was a minor typo in the Windows test script for h5copy. It was actually causing us to do extra work, so this checkin should make the test slightly more efficient, without breaking anything.
Tested:
VS2005 on WinXP
|
| |
|
|
|
|
|
|
|
|
| |
Description:
Previously, the libtest_cstubdll project was creating the DLL in the project directory, rather than the Output directory. This was a simple typo, and not caught previously because past builds had the DLL installed. Cleaning up our batch files will make this easier to catch in the future.
Tested:
VS2005 on WinXP x64
|
|
|
|
|
|
|
|
|
|
|
| |
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:
Previously the process of generating h5tinit.c, as well as the Fortran type files, was very manual on Windows. For Fortran, the process included opening 4 different solutions, and running 4 different commands from the prompt. I've made things very much more automated, and now only requires only building one project for either C or C/Fortran. Running the commands to generate the file is done automatically.
Tested: VS.NET
|
|
|
|
|
|
|
|
| |
Description:
One of the h5diff tests changed to check for NaN values-- this checkin updates our Windows script for these changes.
Tested:
Windows XP
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
Description:
Add new h5import test "teststr" which was added to other platforms this morning.
Tested:
VS.NET on WinXP
|
|
|
|
|
|
|
|
| |
Description:
At a previous seminar, it was brought up that the naming scheme for Windows debug DLL is inconsistent. Specifically, some use *ddll, while others use *dlld. *dlld is more widely-used, so we decided this is "correct". This changes others to use this scheme, and adapts other projects / install scripts / documentation.
Tested:
Visual Studio .NET on WinXP
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
Previously, we needed to force symbol definition "gethostname@8" for compatibility with old versions of Visual Studio. It appears that Visual Studio no longer requires this, so we remove it. This makes the build process on 64-bit much smoother.
Also minor updates to main documentation, command-line documentation, and removed codewarrior and INTEL docs.
Tested:
VS.NET
VS2005
chkmanifest
|
|
|
|
|
|
|
|
|
| |
Description:
h5stat was moved from the ./tools/misc directory to its own directory, so many of our files needed to be updated.
Tested:
VS6 on WinXP
VS.NET on WinXP
|
|
|
|
| |
source code check-in. Tested on .Net and VS 6.0.
|
|
|
|
|
|
|
|
| |
Description:
There was a small typo when I added the new h5stat tests this morning. This corrects it.
Tested:
VS2005 on WinXP x64
|
|
|
|
|
|
|
|
|
|
| |
Description:
- Add new source file H5version.h to Windows projects
- Add new h5stat tests, and uncomment one that no longer fails
- Clean up autotests a little bit.
Tested:
VS.NET on WinXP
|
|
|
|
|
|
|
|
|
|
| |
Description:
This cleans up a lot of different things we were doing in the Windows batch scripts. For one, we now use "exit /b" to better emulate functions in batch scripts. Also changed error-checking to look for negative return values as well.
This also adds initial support for Visual Studio 2005 command-line builds in hdf5build.BAT
Tested:
WinXP
|
|
|
|
|
|
|
|
|
|
| |
Description:
Previously, there was a very intricate process for converting VS6 project files to VS.NET format for testing on the command-line. Now that we maintain VS.NET project files, this system is no longer neccessary. The same builds are now carried out in hdf5build.BAT, so the previous files are obsolete.
Removing them, and updating the MANIFEST
Tested:
WinXP
|
|
|
|
|
|
|
|
| |
Description:
Our Windows test script was using "ERRORLEVEL" to check the diff output for our tooltests. However, FC does not actually set ERRORLEVEL with valid input. As a work around, we pipe the output into FIND, which sets the ERRORLEVEL if it doesn't find a valid string. We probably never saw this bug before because h5dump sets the ERRORLEVEL.
Tested:
WinXP.
|
|
|
|
|
|
|
|
| |
Description:
In the new Windows autotests, hdf5build.BAT was resetting a variable used by hdf5bt.BAT. Changed so hdf5build.BAT looks to see if hdf5bt.BAT is running before it removes this variable.
Tested:
WinXP
|
|
|
|
|
|
|
|
| |
Description:
There was a typo in the new command-line build script that was making it fail early. This should fix it.
Tested:
WinXP
|
|
|
|
|
|
|
|
| |
Description:
I'm in the process of re-writing the Windows build scripts for Visual Studio .NET (and eventually VS2005). These will be used with an autotest script, which is in the works.
Tested:
VS.NET on WinXP, although probably still needs some work.
|
|
|
|
|
|
|
|
| |
Description:
Added new H5WB.c and H5WBprivate.h files to our Windows .NET / 6.0 project files.
Tested:
VS.NET on WinXP
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Description:
Added new H5Dfill.c source file which was added in revision 13918.
|
|
|
|
|
|
|
|
|
|
| |
Description:
Windows does not accept the buffer size parameter of setvbuf to be less than 2. Previously, we had our fix split between two files, H5private.h and the Windows H5pubconf.h. This was a problem for MinGW, because it generates its own H5private.h. This moves the fix out of H5pubconf.h and into H5private.h.
This shouldn't affect other platforms.
Tested:
MinGW on WinXP
|
|
|
|
|
|
|
|
|
|
| |
Description:
Changed a macro in H5FDwindows.c from IO_BUF_SIZE to a more specific WINDOWS_MAX_BUF, and moved it to our H5pubconf.h, where users can customize it to their own preference.
This value is needed because of a bug in the Windows _write function, it is unsafe to write buffers larger than 2GB-1 bytes in one write.
Tested:
VS2005 on WinXP.
|
|
|
|
|
|
|
|
|
|
| |
file driver by default. After thorough testing, we think the windows driver is ready to be included.
I've also updated our Windows documentation file to include 64-bit instructions. The process is fairly tedious right now, but we hope to make it more straight-forward when we depreciate 6.0 and re-work our project files.
Tested:
32-bit WinXP: VS6, VS.NET, and VS 2005
64-bit WinXP: VS.NET and VS 2005
|
|
|
|
|
|
|
|
|
| |
still the default.
Also added a Windows-specific macro, WINDOWS_USE_STDIO, which users can define if they'd like the Windows VFD to use the buffered low-level I/O functions. This is instead of splitting our Windows driver into two separate drivers. By default, this macro is undefined.
Tested:
VS6 on WinXP
|
|
|
|
|
|
|
| |
windows as the default vfd. Although sec2 is still default on Windows, it should now be possible to switch by simply changing H5pubconf.h .
Tested:
.NET 2003 on WinXP
|
|
|
|
|
|
| |
compatible with both .NET and VS2005.
Still needs extensive testing before it's ready.
|
|
|
|
|
|
|
|
|
| |
compatibility, as well as making it compatible for .NET 2003 and VS 6.0. Defined additional macros in H5pubconf.h.
Note that these changes are still not built by default, so shouldn't affect anyone else.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
| |
define the H5_CLEAR_MEMORY macro introduced in rev. 13815.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
| |
replace sec2 as the default driver on Windows. However, it still needs some work right now, and is currently not set to build by default.
Tested:
Visual Studio 2005 (still fails a few tests)
|
|
|
|
|
|
|
| |
#879. This checkin takes care of the first two, I will look at the last one today.
Tested:
Visual Studio 2005 on WinXP
|
|
|
|
|
|
|
| |
update (rev 13775). More work needs to be done to incorporate the new tests.
Tested:
VS6 on Win XP
|
|
|
|
|
|
|
| |
Updated test scripts and MANIFEST accordingly.
Tested:
VS6 on WinXP
|
|
|
|
|
|
|
|
| |
issue with Visual Studio. I've also turned this project on by default in Windows.
Tested:
VS6 on WinXP
kagiso
|
|
|
|
|
|
|
| |
Note: ohdr_gentst currently fails on Windows, and is disabled by default. I'm working with Quincy to get this fixed.
Tested:
VS6 on WinXP
|
|
|
|
|
| |
Tested:
VS 2005 on Win XP
|
|
|
|
|
|
|
| |
updated documentation to reflect changes.
Tested:
Visual Studio 2005 on WinXP
|
|
|
|
|
|
|
|
| |
bring up to date with Linux. Updated MANIFEST for new file added.
Tested:
VS6 on Windows XP
|
|
|
|
|
|
|
| |
include new source files.
Tested:
VS6 on WinXP
|
|
|
|
|
|
|
| |
h52gif and h52gifdll.
Tested:
VS6 and VS2005 on WinXP
|
|
|
|
|
|
|
| |
files toolslib and toolslibD.dsp
Tested:
VS6.0 on Windows XP
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
testhdf5_cpp.dsp and testhdf5_cppdll.dsp received:
./c++/test/tcompound.cpp
./c++/test/ttypes.cpp
./c++/test/tfilter.cpp
./c++/test/tvlstr.cpp
Also, fixed a declaration in ttypes.cpp that was causing a compile error in MSVS6.0.
Tested:
Visual Studio 6.0 on WinXP
kagiso
too minor for h5committest
|
|
|
|
|
|
|
| |
Linux.
Tested:
Visual Studio 6.0 on Windows XP
|
|
|
|
|
|
|
| |
hdf5.dsp and hdf5dll.dsp
Tested:
MSVS6.0 on Win XP
|
|
|
|
|
|
|
| |
hdf5.dsp and hdf5dll.dsp.
Tested:
Visual Studio 6.0 on Windows XP
|
|
|
|
|
|
|
|
|
| |
H5Obtreek.c and H5Odrvinfo.c in hdf5.dsp and hdf5dll.dsp
h5repack_ref.c in h5repack.dsp, h5repackdll.dsp, and h5repacktst.dsp.
Tested:
Visual Studio 6.0 on Windows XP
Visual Studio 8.0 on Windows XP 64-bit
|