| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Also removed unused project settings. These were per file settings that should not be used unless a file needs them.
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
|
|
|
|
| |
Tested: windows
|
|
|
|
|
|
| |
batch file
Tested: XP32 VS2005
|
|
|
|
| |
Tested: Xp64-2005, XP32-VNET
|
|
|
|
| |
using VS2008 Express.
|
|
|
|
| |
(Related to revision 16180)
|
|
|
|
|
|
|
|
|
|
| |
Description:
Recently the new source file H5EAdbkpage.c was added to the main library source code. This checkin also adds it to the Windows project files.
Note: Windows builds are still failing on the earray test, although for other reasons. I'm also looking into this.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
| |
Description:
Recently a new source file, H5Pdapl.c, was introduced. This checkin adds the file to our Windows projects.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
| |
Description:
The source file H5fortran_flags.f90 was recently removed as their symbols were consolidated into the H5E module. We were still referencing the files in Windows, and causing errors. This checkin completely removes references of H5fortran_flags.f90 from Windows.
Tested:
Vs2005 on WinXP
|
|
|
|
|
|
|
|
|
|
| |
Description:
Many new source files were added from the freespace branch. This checkin adds the code to Windows as well.
Note: Some tests are still failing on Windows, but this checkin brings us closer to fixing them. In particular, freespace test fails on compile (Quincey is working on it), and the DLL links test fails at runtime (I'll look into it)
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
| |
Description:
The source file H5EAsblock.c was recently added to svn. This checkin also adds it into our Windows project files.
Note that it hasn't been included in the Visual Studio .NET projects. We are discontinuing our support for Visual Studio .NET in the trunk so we can use C99 features not available in Visual Studio .NET. From this point forward, the Visual Studio .NET projects won't be maintained, and will likely be deleted before the 1.10 release.
|
|
|
|
|
|
|
|
| |
Description:
New source file H5EAdblock.c was added to the library. This checkin adds the file to our Windows projects, hdf5 and hdf5dll (VS2005 and VS.NET project files)
Tested:
Build only, VS2005 on WinXP
|
|
|
|
|
|
|
|
| |
Description:
We recently moved the Windows-specific fortran source code into a separate file for specifying DLL exports. However there were a couple definitions missing in the port from 1.8 to the trunk branch. This checkin correctly includes the .def file into our Windows project, and adds the missing definitions to hdf5_fortrandll.def.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
| |
Description:
This checkin adds the following source files to our Windows projects:
-- H5EAiblock.c
-- H5EAstat.c
-- H5EAdbg.c
|
|
|
|
|
|
|
|
|
| |
for Windows
Description:
In revision 15549, new source code was added for the extensible array interface. This checkin adds the source code to Windows, along with the new test project, earray.
Note: The new H5EA interface causes compilation errors on Windows, and will need to be fixed in the source.
|
|
|
|
|
|
|
|
| |
Description:
There is a new Fortran file, H5_DBLE_InterfaceInclude.f90, which needs to be added to Windows. There is also another version, *InterfaceExclude.f90, which is for users that build with the -r8 flag. However, we don't include this on Windows, as it is not currently a common option. If we get requests from users, we can add documentation for using this alternative interface.
Tested:
VS2005 w/ IVF9.1 on WinXP
|
|
|
|
|
|
|
|
| |
Description:
A new test program, app_ref, was added to the source and configure script. We need to make special Windows project files for static and DLL versions of the test, and also VS2005 and VS.NET versions. Finally, include the new test in our script
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
| |
Description:
A typo in the project output file name was causing Intel Fortran 10.1 to crash. The output file was set to "$(OutDir)\hdf5_fortranddll.dll " (three trailing spaces). IVF 9.1 ignored this error and continued gracefully. However, IVF 10.1 would simply crash. With this fix, we can now build on IVF 10.1 (so far..)
Tested:
VS2008 w/ IVF 10.1 on WinXP
|
|
|
|
|
|
|
|
|
|
| |
dependencies to all_fortran
Description:
The projects testhdf5_1_8fortran[dll] which test the new fortran features in HDF5 1.8 were not registered as dependencies to the "all_fortran" pseudo-project. As a result, the projects would not be built if you simply build all_fortran in Visual Studio, rather than "Build Solution". This is a very minor cleanup, but is neccessary to be consistent in our projects.
Tested:
VS2005 on WinXP x64
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
In library code, we try not to use system calls directly, but instead use the HD{function} macro instead. This way, we can map special versions of the call on particular systems. Previously, it was all done in H5private.h. However, in an effort to clean up platform-specific definitions, we move all of the Windows macros into a separate file, win32defs.h. This way, we can use the non-Posix versions that Visual Studio sends warnings about.
Some macros are set specifically in the platform-specific header files. Then, any macros left unset will be set by the "default" implementation in H5private.h.
This checkin also cleans up various source files to use the HD* macros when possible.
Tested:
VS2005 on WinXP
VS.NET on WinXP
h5committest (kagiso, linew, smirom)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
debug information
Description:
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.
This is another project cleanup and enhancement from user suggestions outlined in bug #1164
Tested:
VS2005 on WinXP
VS.NET on WinXP
|
|
|
|
|
|
|
|
| |
Description:
There were a number of small tweaks we needed to make to add the new fortran_1_8 code on Windows. We create new project files, add new source to them, add the test to our test suite, and fix a few typos in the Windows-specific source code.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
| |
branch back into the trunk (up to revision 14921)
Platforms tested: kagiso with g95 and Intel compilers; more testing will be done after checking in a fresh
copy from the trunk. New code itself was tested with all Fortran compilers available at THG
|
| |
|
|
|
|
| |
New fortran wrappers added.
|
|
|
|
|
|
|
|
| |
Description:
Two new source files have been added, H5Dchunk.c and H5Dscatgath.c. This checkin adds the files to the Windows project files as well.
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
|
|
| |
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, our Windows projects for HL Fortran examples were using outdated library names for our cstub code. As a result, they wouldn't build correctly. This checkin brings them up-to-date.
Also, add hdf5_hl.lib as a dependency to hdf5_hl_fortran.lib. This goes un-noticed when building the complete VS solution, but should be required when only building hdf5_hl_fortran.lib
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
| |
Description:
The ohdr_gentst project exists in order to re-create test input files that are distributed with the source. These projects aren't built by default on most platforms, and the source isn't distributed in release builds. To avoid confusion and bloat, we remove the Windows version of this project.
Tested:
None, only removed
|
|
|
|
|
|
|
|
|
| |
Description:
A new source file has been added, ./test/chunk_info.c. As a result, we need to add new projects for Windows. This includes projects for VS2005 on VNET.
Tested:
VS2005 on WinXP
VNET on WinXP
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Windows project files
Description:
For some reason, the hdf5_hl library didn't have hdf5 listed as a dependency. This isn't normally a problem, because building "all" will build hdf5 library. However, when a user tries to build only hdf5_hl, hdf5 library wouldn't be built.
Although not technically required for compiling the library code, the hdf5 library is needed for linking any applications, so it's a natural dependency.
Tested:
VS2005 on WinXP
VNET on WinXP
|
|
|
|
|
|
|
|
| |
Description:
This catches up Windows to most of the new source files that have been added. Specifically, H5FDpkg.h and H5FDspace.c have been added to the library projects, and tcoords.c has been added to testhdf5. This goes for VS2005 and VS6 project files.
Tested:
Only built, VS2005
|
|
|
|
|
|
|
|
|
| |
project files.
Description: The stream file driver was recently removed from the HDF5-1.8 source. This checkin removes any left-over references in the Windows projects.
Tested:
VS2005
|
|
|
|
|
|
|
|
|
| |
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:
Add toolslib(dll) as a dependency to h5import(dll), to support the new -V flag. This needed to be done in each of our 3 solution files.
Tested:
Only built, VS2005 and VS6
|
|
|
|
|
|
|
|
|
| |
Description:
-- Add new source files to Windows projects: H5Pdeprec.c, H5Pint.c, H5Ddbg.c, H5Dint.c
-- Add new h5dump XML tests to Windows test script
Tested:
VS2005 on WinXP
|
|
|
|
|
|
|
|
| |
Description:
Two new files, h5rdeprec.c and h5rpkg.h were added to the Windows HDF5 projects.
Tested:
VS2005, build only.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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:
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:
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
|
|
|
|
| |
source code check-in. Tested on .Net and VS 6.0.
|
|
|
|
|
|
|
|
|
|
| |
Description:
- Add new source file H5version.h to Windows projects
- Add new h5stat tests, and uncomment one that no longer fails
- Clean up autotests a little bit.
Tested:
VS.NET on WinXP
|
|
|
|
|
|
|
|
| |
Description:
Added new H5WB.c and H5WBprivate.h files to our Windows .NET / 6.0 project files.
Tested:
VS.NET on WinXP
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Description:
Added new H5Dfill.c source file which was added in revision 13918.
|
|
|
|
|
|
|
|
|
| |
still the default.
Also added a Windows-specific macro, WINDOWS_USE_STDIO, which users can define if they'd like the Windows VFD to use the buffered low-level I/O functions. This is instead of splitting our Windows driver into two separate drivers. By default, this macro is undefined.
Tested:
VS6 on WinXP
|
|
|
|
|
|
|
| |
#879. This checkin takes care of the first two, I will look at the last one today.
Tested:
Visual Studio 2005 on WinXP
|
|
|
|
|
|
|
|
| |
issue with Visual Studio. I've also turned this project on by default in Windows.
Tested:
VS6 on WinXP
kagiso
|