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
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:
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:
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
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:
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.
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:
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.
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
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
./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
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
Tested platform:
Kagiso only since it is only a comment block change. If it works in one
machine, it should work in all, I hope. Still need to check the parallel
build on copper.
Tested 1.6 compatibility feature: work for vs studio 6.0
Corrected several small bugs inside tool batch files
Add a few project files to test error APIs
If either szip or zlib filter was not present, the batch still tried to use h5repack tool to test the data compression feature. Therefore the h5repack test failed.
Fixed the bug. Now if the compression filter is not present, that particular repack test will be skipped.
Updates on windows
Tested with
VS C/C++ 6.0 and Compaq fortran 6.6c
VS .Net 2003
Because
1. New source files added to the library
2. New program to test "h5dump -b" option
all.dsw and all.sln need to be updated. all.sln is used only for hdf5bt_net.bat and hdf5bt_intelc.bat.
The previous check-in forgot including the dependency of a new project file.
Updates on windows
Some new source files are added to support new implementation of external links, hdf5dll.dsp needs to updated.
Tested with
VS C/C++ 6.0 and Compaq fortran 6.6c
VS .Net 2003
Some new source files are added to support new implementation of external links, hdf5.dsp needs to updated.
Tested with
VS C/C++ 6.0 and Compaq fortran 6.6c
VS .Net 2003
Because
1. New source files added to the library
2. New program to test "h5dump -b" option
all.dsw and all.sln need to be updated. all.sln is used only for hdf5bt_net.bat and hdf5bt_intelc.bat.
Update windows project file
Description:
Eliminate the link to non-existing HL headers.
Solution:
Platforms tested:
windows MSVS 6.0
Won't affect other platforms and too minor to check with other windows compilers.
Misc. update:
Update HDF5 Fortran90 type definition file on windows to
reflect the changes in Linux.
Description:
INT has been changed to Fortran_INTEGER in the file.
Solution:
Make the change.
Platforms tested:
Visual fortran 6.6c with MSVS 6.0
Only affects windows.
Misc. update:
Updating project file
Description:
Due to the new added source codes under hdf5/src.
Solution:
Project file has to be changed to reflect this
Platforms tested:
VS 6.0 ( Failed during compiling because of compiler failure)
VS 7.0
Everything okay except that several h5repack tests get skipped.
Don't know whether this happens on other platforms.
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -f dset_none:S+O=31 -
SKIPED-
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -SKIP
ED-
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -f dset_scaleoffset:N
ONE -SKIPED-
h5repack -i test_all.h5 -o out.test_all.h5 -SKIP
ED-
Misc. update:
Updating project file
Description:
New source code has been added,
project files need to be updated.
Solution:
Platforms tested:
VS 6.0(build failed due to compiler problem)
VS 7.1(.Net 2003)
Everything okay except that several h5repack tests get skipped.
Don't know whether this happens on other platforms.
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -f dset_none:S+O=31 -
SKIPED-
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -SKIP
ED-
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -f dset_scaleoffset:N
ONE -SKIPED-
h5repack -i test_all.h5 -o out.test_all.h5 -SKIP
ED-
Misc. update:
Updating the windows DLL project file
Description:
new file H5HFiter.c has been added
project file needs to be reflected
Solution:
Platforms tested:
VSMS 6.0
Misc. update:
Updating windows project file
Description:
new file H5HFiter.c has been added
project file needs to be reflected
Solution:
Updating the project file
Platforms tested:
VS 6.0
Misc. update:
Maintenance on Windows
Description:
change delimiter between preprocessor names from " " to ",".
Interl fortran doesn't take " " as delimiter.
Solution:
Platforms tested:
Misc. update:
Maintenance on Windows
Description:
All of the source code files were replaced by a new one.
Solution:
Platforms tested:
Windows XP with VS 6.0
Misc. update:
Update DLL project file
Description:
New source files are added, DLL project needs to be updated to reflect the change.
Solution:
Platforms tested:
windows XP VS 6.0 C and C++
Misc. update:
update project file on windows
Description:
New files have been checked in, library project files have to be updated.
Solution:
Platforms tested:
windows XP with 6.0
Misc. update:
Maintenance on Windows
Description:
Fix a echo error:
when running lstest.bat, previously echo "h5dump ..."
change it to "h5ls ..."
Solution:
Platforms tested:
Misc. update:
Maintenance on Windows
Description:
Temporarily comment out echo error messages to the screen for checking autotests
on windows.
Solution:
Platforms tested:
Misc. update:
Maintenance on Windows
Description:
Change output for skip tests from "SKIP" to "-SKIP-" for easier tell the skiped tests
Solution:
Platforms tested:
Windows XP
Misc. update:
Maintenance on Windows
Description:
Change dll projects output path and
let output of dll projects generated into a separate
directory from static projects
Solution:
Platforms tested:
Windows XP
Misc. update:
Maintenance on Windows
Description:
Add in new h5dump tests (tvms.ddl tvms.h5 Checked in by Pedro)
Skip new h5dump tests ( tldouble.h5 checked in by Pedro)
Solution:
Platforms tested:
Windows XP
Misc. update:
Maintenance on Windows
Description:
update batch file according to Pedro's bug fix (h5dump was not printing attributes for the named datatype cases)
Solution:
Platforms tested:
Windows XP
Misc. update:
portable issue on windows
Description:
setvbuf on visual studio 2005 needs the size to be greater or equal to 2.
<description of setvbuf from msdn library>
Buffer size in bytes. Allowable range: 2 <= size <=
INT_MAX (2147483647). Internally, the value supplied
for size is rounded down to the nearest multiple of 2.
h5import used linebuffer option of setvbuf for stderr and stdout and the size is
0 by default. This causes core dump with visual 2005 on windows 64-bit.
Solution:
1. Use HDsetvbuf inside h5import.c,
2. Define HDsetvbuf inside windows H5pubconf.h for windows to work around
the core dump of h5import test. This is probably a bug inside visual studio 2005.
Platforms tested:
h5commit(shanti is down)
VS 6.0 on windows XP
VS 8.0 on windows XP-64bit
Misc. update:
