| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Tested: windows
|
|
|
|
| |
Tested: Notepad
|
|
|
|
|
|
|
|
|
|
| |
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:
When specifying library search path in Visual Studio, use the DLL folder for zlib. Previously we pointed to the "lib" folder, which was causing confusion.
|
|
|
|
|
|
|
|
|
|
|
|
| |
and Windows command line
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
|
|
|
|
| |
recommendations.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
-- INSTALL_Windows.txt:
-- Update szip version number to 2.1
-- Extra details for setting up 64-bit builds
-- Explain adding HDF5 link settings more clearly
-- Add link to FAQ
-- Misc. typos and formatting
-- INSTALL_Windows_From_Command_Line.txt
-- Add note about 64-bit support
-- INSTALL_Windows_Short_NET.TXT
-- Add notes detailing features unsupported on VS.NET
-- INSTALL_Windows_Short_VS2005.TXT
-- Add notes about extra features.
|
|
|
|
|
| |
Description:
Small changes to the documentation-- update version strings to 1.8.1 and document the HDF5TestExpress variable
|
| |
|
|
|
|
| |
New fortran wrappers added.
|
|
|
|
|
| |
Description:
List the new HL C examples that were added in the last checkin. Rather than listing each one individually, we give a brief summary, and instructions for how to test them.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
platforms
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:
Wrote documentation on how to use the 1.6 API for a user application-- this replaces the outdated documentation we previously had.
Tested: VS2005 with HDFEOS5
|
| |
|
|
|
|
|
| |
Details:
We no longer support Visual Studio 6.0, so we note it in the documentation. Also, updated the path references in VS.NET documentation
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
H5detect.c
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.
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Fortran configuration in today's earlier checkin. Also removed documentation for the stdio driver, as it is currently broken.
|
|
|
|
|
| |
Tested:
VS 2005 on Win XP
|
|
|
|
|
|
|
| |
updated documentation to reflect changes.
Tested:
Visual Studio 2005 on WinXP
|
|
|
|
| |
Mostly just correcting typos, no testing needed.
|
|
|
|
|
|
|
| |
well as a typo in the zlib instruction.
Tested:
VS 6.0 on WinXP
|
|
|
|
|
|
| |
libraries.
No testing needed.
|
|
|
|
| |
No testing needed.
|
|
|
|
|
|
| |
Compiler support, as well as our depreciation of previous versions of the Intel Compiler.
No testing needed.
|
| |
|
|
|
|
|
| |
limitation of support 64-bit with visual studio 2005
How to test with 1.6 compatible
|
|
|
|
| |
of HDF5 on windows 64-bit platform.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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:
Update contents on HL C Examples
Solution:
Platforms tested:
Misc. update:
|
|
|
|
|
|
|
|
|
|
|
| |
Maintenance on Windows
Description:
Document update to reflect recent changes
Solution:
Platforms tested:
Misc. update:
|
|
|
|
|
|
|
|
|
|
|
| |
Maintenance on Windows
Description:
Add in instruction for building hl fortran examples
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:
|
|
|
|
|
|
|
|
|
|
|
| |
Maintenance on windows
Description:
some typoes
Solution:
Platforms tested:
Misc. update:
|
|
|
|
|
|
|
|
|
|
|
| |
Maintenance on Windows
Description:
Reformat a little bit to make it easy to read and find
Solution:
Platforms tested:
Misc. update:
|