| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
New fortran wrappers added.
|
| |
|
|
|
|
|
|
|
|
| |
Description:
On Windows, many POSIX functions have been replaced by a similarly-named function with some additional security-checking. Visual Studio issues a warning each time the POSIX version is used, recommending that we replace it with the new version. This results in thousands of errors when building the HDF5 library.
This checkin adds a Visual Studio "Property Sheet", which has been applied to all library projects, and defines a number of preprocessors to suppress these warnings. The warnings have been disabled only in Visual Studio 2005 project files, as VS.NET doesn't support property sheets.
Tested:
VS2005 on WinXP
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
be "CRLF"
instead of "native".
|
| |
|
|
|
|
|
|
|
|
|
| |
Update typegen.sln
Description:
Solution:
Platforms tested:
MSVS .Net on windows XP
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Support command line build HDF5 with Visual C++ .Net and Intel compiler
Description:
We can not find a way to convert workspace to solution format from command line.
typegen.sln will be provided in order to support command line build HDF5
with MSVS .Net and Intel Compiler.
Solution:
Platforms tested:
MSVS .NET on windows XP.
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Update project files to generate H5fortran_detect.f90
Description:
Source code in project file H5fortran_detect_gen.dsp was renamed
to H5test_kind.f90.
Solution:
Platforms tested:
Compaq fortran 6.6 on windows XP.
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
| |
Update project setting.
Description:
Solution:
Platforms tested:
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
| |
Use to generate H5f90i_gen.h and H5fortran_types.f90
Description:
Special project file for windows.
Solution:
Platforms tested:
MSVS 6.0 on windows XP.
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
| |
Use to generate H5f90i_gen.h and H5fortran_types.f90 on windows.
Description:
Special workspace for windows.
Solution:
Platforms tested:
MSVS 6.0 on windows XP.
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
| |
Use to generate H5fortran_detect.f90 in windows.
Description:
Special workspace for windows.
Solution:
Platforms tested:
MSVS 6.0 on windows XP.
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
| |
Use to generate H5fortran_detect.f90
Description:
Special project file on windows XP.
Solution:
Platforms tested:
MSVS 6.0 on windows XP.
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
| |
Use to generate H5fort_type_defines.h in windows.
Description:
Special project file for windows.
Solution:
Platforms tested:
MSVS 6.0 on windows XP.
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
| |
Special wrokspace for windows.
Description:
Use to generate H5fort_type_defines.h in windows.
Solution:
Platforms tested:
MSVS6.0 on windows XP.
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
| |
Typo in directory name.
Description:
Solution:
Platforms tested:
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Adding windows project files to simulate the fortran auto-type conversion procedures on linux.
Description:
Solution:
Platforms tested:
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Adding windows workspace to simulate the fortran auto-type conversion procedures on linux.
Description:
Solution:
Platforms tested:
windows xp
Misc. update:
|
| |
|
|
|
|
|
|
|
|
|
| |
For windows support, remove all.zip from hdf5.
Description:
Add h5tinit project file into windows/misc/typegen/h5tinit
Solution:
Platforms tested:
MSVS 6.0 on windows xp.
Misc. update:
|
|
|
For windows support, remove all.zip from hdf5.
Description:
Add typegen workspace project file into windows/misc/typegen
Solution:
Platforms tested:
MSVS 6.0 on windows xp.
Misc. update:
|
