| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
| |
the windows batch files.
|
| |
|
|
|
|
| |
command line.
Tested: windows
|
| |
|
|
|
|
|
|
| |
Deleted obsolete vnet project files as it is no longer supported for HDF55 1.9 and above
Removed references from batch build files.
Release documents still need to be updated.
Tested XP32 VS2005
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
| |
command line
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
|
| | |
|
| |
|
|
| |
New fortran wrappers added.
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
| |
script
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:
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:
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:
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.
|
| | |
|
| |
|
|
|
|
| |
be "CRLF"
instead of "native".
|
| |
|
|
|
|
|
|
|
|
|
| |
Add in copyright information
Description:
Solution:
Platforms tested:
Windows XP
Misc. update:
|
|
|
Remove all.zip for supporting windows.
Why?
1. Avoid confliction for windows programmers
2. Decrease size of CVS tree by adding all.zip
3. Avoid using winzip as the intermediate step
Kent Yang
Description:
Put all windows project files under hdf5/windows directory.
This check-in includes some batch files.
Solution:
Platforms tested:
VS 6.0, windows XP
Misc. update:
|
