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:
We recently uploaded new versions of our external library binaries to support more compiler configurations. This check-in is to point to the new location in our documentation.
Tested:
None
Description:
There are minor changes in the testing process for Windows with the new test scripts. Specifically, the test output is output to the screen, rather than redirected into files, by default. Also, it is much easier to test parts modularly, and installing DLLs is one step, instead of separated batch files.
Tested:
None, only documentation changed.
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:
Visual Studio does not have the function siglongjmp. Therefore, we have created a new configure flag H5_HAVE_SIGLONGJMP that tests for this. We use this within H5detect.c.
Tested:
VS.NET
h5committest
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:
The Windows documentation on generating H5tinit.c was lacking special instructions for Visual Studio 2005. Specifically, Windows does not support the function "siglongjmp". Previous versions of Visual Studio will ignore this function, but VS2005 produces an error.
Tested:
VS6
VNET
VS2005
Description:
Explain why Fortran isn't supported on MinGW and give users an "unsupported" alternative. Also re-worked the main documentation to clarify using the HDF5 DLL libraries.
Tested:
None needed.
Description:
This makes major updates to the Windows installation documentation, to account for the switch from VS6 to .NET. Installation instructions for 6.0 can also be found in INSTALL_Windows_Short_MSVS6.0.TXT, although it's noted that we are phasing out our VS6 support.
Also added install instrctions for MinGW, to reflect our initial support. Updated MANIFEST for new file checkin.
Tested:
Instructions for each configuration have been tested.
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
Maintenance on Windows
Description:
ttsafedll will be automatically enabled when using .Net and Intel
Add in some instructions for this in applicable places
Solution:
Platforms tested:
Misc. update:
Maintenance on Windows
Description:
hdf5_hl_fortran is a mixed language project. when building
this project , the compiler will ask to choose one language as a main
project.
Missed this information in previous document.
Need to ch
Solution:
Platforms tested:
Misc. update:
Correcting typos and updating
Description:
Several section numbers are messed up inside INSTALL_Windows.txt.
Remove the section of using DEBUG information inside HDF5 since it is difficult to verify whether this part of code is indeed used. Most people use windows' own debugger while debugging.
Solution:
Platforms tested:
Misc. update:
Maintenance on Windows
Description:
Add how to build hdf5 with thread-safe feature on windows into the
document
Solution:
Platforms tested:
Misc. update:
Update documents about installing hdf5 on windows xp
Description:
Modified files: INSTALL_Windows.txt INSTALL_Windows_From_Command_Line.txt
INSTALL_Windows_Short.txt
Solution:
Platforms tested:
Misc. update:
Update.
Description:
Update installation file on how to link HDF5 with Zlib 1.2.2 and Szip 2.0 DLL libraries.
Solution:
Platforms tested:
Misc. update:
Update.
Description:
Update HDF5 Windows installation documentation to include recently added HDF5 high level library and tests information.
Solution:
Platforms tested:
Not necessary.
Misc. update:
Add more contents related to szip
Fix other bugs
Description:
Describe where to find szip, how to turn off szip compression.
Solution:
Platforms tested:
Misc. update:
Update install_windows.txt.
Description:
the description of using the allexample.dsw needs to be modified with
the addition of szip to HDF5 library.
Some typos are corrected.
Solution:
Platforms tested:
Misc. update:
Add decriptions to use libtestD.dll.
Description:
libtestD.dll should be placed to a place that the user can find in order to
test HDF5 DLL within HDF5 workspace.
Solution:
Explained in document.
Platforms tested:
No need
Misc. update:
Add a little more comments on where to put DLL.
Description:
User can put HDF5DLL in the place where the application can find.
It doesn't have to be at system directory.
Solution:
Add comments to "only suggest the user to use system directory".
Platforms tested:
text file, no need to be tested.
Misc. update:
