| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
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:
|
