Description:
These changes are made via a user's suggestion, bugzilla bug #1164. These have all been tested in the trunk, and are stable/favorable changes.
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. We remove the ignored library from the project files. This actually makes no difference in the output binaries.
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.
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
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.
Tested:
VS2005 on WinXP
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:
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
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
For windows support, remove all.zip form hdf5.
Description
Add fortran example project files into hdf5/windows/fortran
Solution:
Platforms tested:
Comapq Visual Fortran 6.0 on windows xp.
Misc. update:
For windows support, remove all.zip form hdf5.
Description:
Add fortran example project files into hdf5/windows/fortran
Solution:
Platforms tested:
Comapq Visual Fortran 6.0 on windows xp.
Misc. update:
For windows support, remove all.zip from hdf5.
Description:
Add fortran example project files into hdf5/windows/fortran.
Solution:
Platforms tested:
Comapq Visual Fortran 6.0 on windows xp.
Misc. update:
For windows support, remove all.zip from hdf5.
Description:
Add fortran examples project files into hdf5/windows/fortran
Solution:
Platforms tested:
Compaq Visual Fortran 6.0 on windows xp.
Misc. update:
For windows support, remove all.zip from hdf5.
Description:
Add fortran examples project file into hdf5/windows/fortran.
Solution:
Platforms tested:
Comapq Visual Fortran 6.0 on windows xp.
Misc. update:
For windows support, remove all.zip from hdf5.
Description:
Add fortran examples project file into hdf5/windows/fortran.
Solution:
Platforms tested:
Compaq Visual Fortran 6.0 on windows xp.
Misc. update:
For windows support, remove all.zip from hdf5.
Description:
Add fortran example project files into hdf5/windows/fortran
Solution:
Platforms tested:
Compaq Visual Fortran 6.0 on windows xp.
Misc. update:
For windows support, remove all.zip from hdf5.
Description:
Add fortran examples project file into hdf5/windows.
Solution:
Platforms tested:
Compaq Visual Fortran 6.0 on windows xp.
Misc. update:
For windows support, remove all.zip from hdf5.
Description:
Add fortran examples project file into hdf5/windows.
Solution:
Platforms tested:
Compaq Visual Fortran on windows xp.
Misc. update:
For windows support, remove all.zip from hdf5.
Description:
Add fortran example project files into hdf5/windows.
Solution:
Platforms tested:
Compaq Visual Fortan.
Misc. update:
For windows support, remove all.zip from hdf5.
Description:
Add fotran example project files into hdf5/windows
Solution:
Platforms tested:
Compaq Visual Fortan 6.0
Misc. update:
