Description:
The source file H5fortran_flags.f90 was recently removed as their symbols were consolidated into the H5E module. We were still referencing the files in Windows, and causing errors. This checkin completely removes references of H5fortran_flags.f90 from Windows.
Tested:
Vs2005 on WinXP
Description:
Two new test cases for h5dump were recently added to the test script on Unix. This checkin also adds the new cases to Windows.
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)
Description:
The general h5ls test script was recently updated. This checkin brings those changes to Windows
Also add freespace & mf to general test script, since I forgot in the last checkin
Tested:
VS2005 on WinXP
Description:
Many new source files were added from the freespace branch. This checkin adds the code to Windows as well.
Note: Some tests are still failing on Windows, but this checkin brings us closer to fixing them. In particular, freespace test fails on compile (Quincey is working on it), and the DLL links test fails at runtime (I'll look into it)
Tested:
VS2005 on WinXP
Description:
The source file H5EAsblock.c was recently added to svn. This checkin also adds it into our Windows project files.
Note that it hasn't been included in the Visual Studio .NET projects. We are discontinuing our support for Visual Studio .NET in the trunk so we can use C99 features not available in Visual Studio .NET. From this point forward, the Visual Studio .NET projects won't be maintained, and will likely be deleted before the 1.10 release.
Description:
Add a new test for h5import to check for alignment. Also fix the failing h5repack test, now that ublock has been added to svn.
Tested
VS2005 on WinXP
Description:
New source file H5EAdblock.c was added to the library. This checkin adds the file to our Windows projects, hdf5 and hdf5dll (VS2005 and VS.NET project files)
Tested:
Build only, VS2005 on WinXP
Description:
earray[dll] builds were failing on Windows because of missing link dependencies to szip and zlib libraries (amongst other reasons). This checkin adds those dependencies.
Description:
We recently moved the Windows-specific fortran source code into a separate file for specifying DLL exports. However there were a couple definitions missing in the port from 1.8 to the trunk branch. This checkin correctly includes the .def file into our Windows project, and adds the missing definitions to hdf5_fortrandll.def.
Tested:
VS2005 on WinXP
Description: Added configure test to see if pointer alignment restrictions are enforced (as in dereferencing an unaligned pointer causes an error). Added code in H5Tvlen.c to avoid dereferencing unaligned pointers, conditionally compiled based on the configure test. Added test case in dtypes.c which would previously cause such machines to fail.
Tested: kagiso, smirom, linew (h5committest); linew64
Description:
In some of the new H5EA* code, many new C99 features are being used. Most of them are portable to all compilers, but the __func__ keyword in particular isn't supported in Visual Studio on Windows. Instead, Windows defines the __FUNCTION__ keyword, which can be used as a direct substitute.
We now check for the __func__ keyword during configure and define the feature flag H5_HAVE_C99_FUNC. There was previously a check for __FUNCTION__, and the feature flags H5_HAVE_FUNCTION. In H5EApkg.h, we check for the presents of each of these in order to see which to use. If neither are avaiable, fail.
Tested:
h5committest (kagiso, smirom, linew)
Description:
New h5repack tests were added in revision 15551 and 15557, and also the syntax of one test was changed. This was causing errors on Windows. This checkin should fix those errors.
Tested:
VS2005 on WinXP
Description:
In revision 15549, new source code was added for the extensible array interface. This checkin adds the source code to Windows, along with the new test project, earray.
Note: The new H5EA interface causes compilation errors on Windows, and will need to be fixed in the source.
Description:
There is a new Fortran file, H5_DBLE_InterfaceInclude.f90, which needs to be added to Windows. There is also another version, *InterfaceExclude.f90, which is for users that build with the -r8 flag. However, we don't include this on Windows, as it is not currently a common option. If we get requests from users, we can add documentation for using this alternative interface.
Tested:
VS2005 w/ IVF9.1 on WinXP
Description:
A new test program, app_ref, was added to the source and configure script. We need to make special Windows project files for static and DLL versions of the test, and also VS2005 and VS.NET versions. Finally, include the new test in our script
Tested:
VS2005 on WinXP
Description:
This commit is a major update to the Windows-maintained H5pubconf.h file. This file is statically-distributed because Windows cannot generate it dynamically as other platforms do. Previously, our Windows version contained a minimal subset of the macro definitions required. To update, I've gone through each macro (based on kagiso's output), and tested for the correct value on Windows. This allows us to better target code based on feature flags. It should also be easier to update in the future as changes are made to the configure script.
This commit also contains one small bug fix in h5ls.c. Some Windows-specific code was missing a local variable definition. The bug went unnoticed because Windows didn't define the feature flag correctly.
I've also made changes to the h5vers script. Whenever the version string is incremented (automatically by h5test after a snapshot), the strings in H5pubconf.h will also be updated.
Tested:
VS2005 on WinXP (32- and 64-bit)
VS.NET on WinXP 32-bit
h5vers tested under Cygwin
Description:
A new parameter was added to h5diff recently. We add a new test to the h5diff script, and change the syntax in which h5diff is called from the h5repack test script
Tested:
VS2005 on WinXP
Description:
The testfiles directory moved, so we need to update test script on Windows. This should fix the Windows daily-test errors from the weekend.
Tested:
VS2005 on WinXP
Description:
Write documentation for building HDF5 with the latest version of Visual Studio, 2008. The process is very similar to building with Visual Studio 2005, but with an automatic project-file conversion beforehand.
Also adapt commandline build scripts for Visual Studio 2008 as well.
Tested:
VS2008 on WinXP
Description:
Modify Windows documentation to support Intel Visual Fortran 10.1. We have tested it in our Virtual machines, and have fixed the problems we were encountering.
Also, add a new parameter to the hdf5build.BAT and hdf5bt.BAT build scripts to support IVF 10.1.
Tested:
VS2005 with IVF 9.1 and 10.1 on 32-bit XP
Description:
On Windows, we manage dynamically-generated code through "post-build" steps in Visual Studio. However, the command for it wasn't checking to see if the code already existed, so it was re-generating in each build (and thus re-generating all dependencies). To overcome, we simply check if the source file exists before generating it.
Also, put all paths inside quotes so we can handle directory names with spaces.
Tested:
VS2005 on WinXP
Description:
A typo in the project output file name was causing Intel Fortran 10.1 to crash. The output file was set to "$(OutDir)\hdf5_fortranddll.dll " (three trailing spaces). IVF 9.1 ignored this error and continued gracefully. However, IVF 10.1 would simply crash. With this fix, we can now build on IVF 10.1 (so far..)
Tested:
VS2008 w/ IVF 10.1 on WinXP
Description:
The fillval test uses random input to test various fill cases. Certain boundary cases cause the test to fail, which produces sporadic errors on Windows. There is a bug filed for the issue here:
http://bugzilla.hdfgroup.uiuc.edu/show_bug.cgi?id=1155
We will disable the test until the bug is fixed.
Tested:
None, simply disabled.
Description:
More updates were made to the h5diff test script structure. Specifically, the printing of output and how files are found in the actual test. This brings the changes to Windows as well.
Tested:
VS2005 on WinXP
Description:
The testfiles for h5diff were moved the a new folder, and the general script was updated. This checkin makes the minor changes neccessary for Windows to use the new folder.
Tested:
VS2005 on WinXP
Description:
As part of our Windows cleanup, we try to remove windows-specific tweaks in the source code. There are many instances where Windows code is introduces via ifdef's. We re-evaluate whether they are still required, and found that many of them are not. Others we change to "feature"-specific code, rather than Windows-specific.
Tested:
VS2005 on WinXP
VS.NET on WinXP
h5committest (kagisopp, smirom, linew)
Description:
The projects testhdf5_1_8fortran[dll] which test the new fortran features in HDF5 1.8 were not registered as dependencies to the "all_fortran" pseudo-project. As a result, the projects would not be built if you simply build all_fortran in Visual Studio, rather than "Build Solution". This is a very minor cleanup, but is neccessary to be consistent in our projects.
Tested:
VS2005 on WinXP x64
Description:
In library code, we try not to use system calls directly, but instead use the HD{function} macro instead. This way, we can map special versions of the call on particular systems. Previously, it was all done in H5private.h. However, in an effort to clean up platform-specific definitions, we move all of the Windows macros into a separate file, win32defs.h. This way, we can use the non-Posix versions that Visual Studio sends warnings about.
Some macros are set specifically in the platform-specific header files. Then, any macros left unset will be set by the "default" implementation in H5private.h.
This checkin also cleans up various source files to use the HD* macros when possible.
Tested:
VS2005 on WinXP
VS.NET on WinXP
h5committest (kagiso, linew, smirom)
Description:
Previously, we maintained some source files that are commonly generated dynamically on other systems. Now, we also generate them on Windows as well. We should remove them from the repository so old versions are not accidentally used.
Also, clean up the project files to organize generator programs.
Tested:
VS2005 on WinXP
VS2005 on WinXP x64
VS.NET on WinXP
Description:
In some rare instances, FC (diff equivalent) command on Windows will fail when comparing ASCII files with opposite line-ending formats (Unix uses LF, while Windows uses CRLF). This was an issue for one test case in our test script. It only came up when testing from a release tarball, because the expected output was not converted to Windows-style. In this situation, FC was reporting false differences.
To workaround, we double-check failure cases and convert the EOL characters if neccessary.
Tested:
VS2005 on WinXP
Description:
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
no need to test other platforms, Windows-specific source change
Description:
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.
This is another project cleanup and enhancement from user suggestions outlined in bug #1164
Tested:
VS2005 on WinXP
VS.NET on WinXP
Description:
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. Per a user's suggestion, we remove the ignored library from the project files. This actually makes no difference in the output binaries.
Tested:
VS2005 on WinXP
VS.NET on WinXP
Description:
In our Windows command-line build script, we now support building with Visual Studio .NET, although VS2005 is still the default. Building with VS.NET still imposes the same feature restrictions as through the IDE:
-- 64-bit builds are unsupported
-- Fortran is unsupported
Tested:
VS.NET on WinXP
VS2005 on WinXP
Description:
The source file tf.f90 now produces a module error_handler.mod, which was being created in a wrong directory. As a result, Visual Studio couldn't find it, and building failed. This corrects the module path of libtestdll project.
Tested:
VS2005 on WinXP
Description:
We can dynamically detect the host architecture using the PROCESSOR_ARCHITECTURE variable. This allows us to setup our build paths accordingly and build 64-bit Windows binaries from the command line. This allows us to run autotests on 64-bit Windows as well.
Tested:
VS2005 on WinXP x64
VS2005 on WinXP x86
Description:
There were a number of small tweaks we needed to make to add the new fortran_1_8 code on Windows. We create new project files, add new source to them, add the test to our test suite, and fix a few typos in the Windows-specific source code.
Tested:
VS2005 on WinXP
Platforms tested: kagiso with g95 and Intel compilers; more testing will be done after checking in a fresh
copy from the trunk. New code itself was tested with all Fortran compilers available at THG
Description:
Two new source files have been added, H5Dchunk.c and H5Dscatgath.c. This checkin adds the files to the Windows project files as well.
Tested:
VS2005 on WinXP
Description:
When building HDF5 with thread safety on Windows, the err_compat test was failing because our output was being parsed incorrectly. Rather than having a thread number in the error stack trace, there will be the string "some thread: no way to know the thread (IDs): from pthread on windows:". This checkin now takes this into account, and modifies the output accordingly.
Tested:
VS2005 on WinXP with Pthreads
Description:
On Windows, many POSIX functions have been replaced by a similarly-named function with some additional security-checking. Visual Studio issues a warning each time the POSIX version is used, recommending that we replace it with the new version. This results in thousands of errors when building the HDF5 library.
This checkin adds a Visual Studio "Property Sheet", which has been applied to all library projects, and defines a number of preprocessors to suppress these warnings. The warnings have been disabled only in Visual Studio 2005 project files, as VS.NET doesn't support property sheets.
Tested:
VS2005 on WinXP
Description:
Just as we have scripts for building and testing the HDF5 library on Windows, hdf5build_examples.BAT is a new script for building HDF5 example projects on Windows. This is especially useful for our new Windows Daily Tests, to test our examples automatically as well.
Eventually, we will have hdf5check_examples.BAT and hdf5bt_examples.BAT to test our examples as well.
Tested:
VS2005 on WinXP
Description:
Previously, our Windows projects for HL Fortran examples were using outdated library names for our cstub code. As a result, they wouldn't build correctly. This checkin brings them up-to-date.
Also, add hdf5_hl.lib as a dependency to hdf5_hl_fortran.lib. This goes un-noticed when building the complete VS solution, but should be required when only building hdf5_hl_fortran.lib
Tested:
VS2005 on WinXP
Description:
In the Windows Fortran example projects, the runtime library used for linking static-debug version was set incorrectly. This was a result of the project being upgraded from VS6 where we used Single-threaded libraries. Those libraries are no longer supported, so we use [Debug] Multithreaded [DLL] now instead.
Note that this also needs to be updated in the VS.NET project files-- I will make those changes shortly.
Tested:
VS2005 on WinXP
Description:
Many new path-specific tests have been added via the "links" test. Because Windows' path format is non-standard, we need a special macro defined to handle it specially. Note that 2 tests still fail with this macro defined, but it should be fixed soon.
Tested:
VS2005 on WinXP
Description:
The ohdr_gentst project exists in order to re-create test input files that are distributed with the source. These projects aren't built by default on most platforms, and the source isn't distributed in release builds. To avoid confusion and bloat, we remove the Windows version of this project.
Tested:
None, only removed
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:
A new source file has been added, ./test/chunk_info.c. As a result, we need to add new projects for Windows. This includes projects for VS2005 on VNET.
Tested:
VS2005 on WinXP
VNET on WinXP
Description:
As pointed out by a user, we added an un-needed link directory for szip which is machine-dependent and, in his case, problematic. We can safely remove this reference because we already include the szip link directory elsewhere.
Tested:
None, simply removed
Description:
A commented test was deleted from the main h5dump test script. This makes the same change in the Windows script. This won't actually make any noticeable changes-- just to keep up with Linux.
Tested:
None needed, no new tests, just deleted comments
Description:
A small typo in the recent update to installhdf5lib.bat caused the C++ header files not to be installed for the debug version of the libraries. This corrects the issue.
Tested:
VS2005 on WinXP
Description:
The names of the test files for h5import changed slightly, so we needed to update our test script accordingly. Also, a test for EOL characters has been added.
Tested:
VS2005 on WinXP
Description:
The Windows suite of examples for HL C was a very small subset of the examples that exist for other platforms. Now we have all of the HL C examples-- integrated into the VS projects files, and batch test scripts.
Tested:
VS2005 on WinXP
VNET on WinXP
Description:
The collection of HL C examples that we distribute for Windows is incomplete. I wasn't aware of it until Pedro pointed it out, because we use different (although similar) names for the generated files. This checkin changes the naming to follow Linux, in preparation to add the rest of the HL examples to Windows.
Note: I believe I've updated the MANIFEST accordingly, but I may have missed something-- I'll check on Linux shortly after this commit.
Tested:
VS2005 on WinXP
VS.NET on WinXP
Description:
For some reason, the hdf5_hl library didn't have hdf5 listed as a dependency. This isn't normally a problem, because building "all" will build hdf5 library. However, when a user tries to build only hdf5_hl, hdf5 library wouldn't be built.
Although not technically required for compiling the library code, the hdf5 library is needed for linking any applications, so it's a natural dependency.
Tested:
VS2005 on WinXP
VNET on WinXP
Description:
Previously, all of our build output would simply go to stdout/stderr for command-line builds. We can pipe this into a log file as a whole, but the complete logfile becomes very large very quickly. Instead, we give the user an option to place build results and test results into separate logs (or even the same). This will help keeping track of results in our automated testing.
Tested:
VS2005 on WinXP
Description:
A user pointed out that one of our Fortran dependencies wasn't getting installed correctly due to a wrong path in our install file. After reviewing, I've applied the patch that he's proposed.
Description:
For some reason, the h5reparttst output folder wasn't set correcty for 64-bit Windows. This may have gotten accidentally changed with other intermediate project file changes.
Tested:
VS2005 on WinXP x64
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:
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.
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:
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
Details:
We no longer need to parse the h5ls output to remove "Modified" tags. This makes it much easier to test on Windows, because we don't need to emulate `sed`.
Tested:
VS2005 on WinXP
Description:
Larry was able to track down the bug in the h5ls test script and change it around to check for an expected error code for each test. With this, we are now able to uncomment the broken test on Windows.
Tested:
VS2005 on WinXP
Description:
The h5ls test script was recently updated on Linux. This makes the same changes on Windows. Also, we had to comment out one of our tests, because h5ls returns an error-code that is giving false-positives.
Tested:
VS2005 on WinXP
Description:
Minor changes were recently made in the linux test scripts for h5diff and h5repack. This brings Windows up-to-date.
Note: I am still working on updates to testh5ls.bat-- there is one test that is failing, but should be ready soon.
Tested:
VS2005 on WinXP
Description:
h5repack_list.c was deleted from the repository recently. This check-in also removes references in the Windows library.
Tested:
Built with VS2005
Description: The stream file driver was recently removed from the HDF5-1.8 source. This checkin removes any left-over references in the Windows projects.
Tested:
VS2005
Description:
Recently, the format of parameters for h5diff was changed. This checkin makes the neccessary changes for Windows to also bring it up to date.
Tested:
VS6 on WinXP
Description:
Previously, we provided a static h5tinit.c with our Windows distribution, and provided instructions to optionally generate it. Now, we will incorporate it as part of the default build process, to emulate other platforms more closely.
Tested:
VS6
VS2005
Description:
Add toolslib(dll) as a dependency to h5import(dll), to support the new -V flag. This needed to be done in each of our 3 solution files.
Tested:
Only built, VS2005 and VS6
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:
This updates the command-line build process to handle structural changes we've made in the HDF5 project files. Also, we add support for two new options:
/fort - to build Fortran libraries
/useenv - to allow users to specify include and libpath directories on the command line as well.
Also updated documentation to reflect these change.
Tested:
VS2005 on WinXP
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.
