summaryrefslogtreecommitdiffstats
path: root/windows/fortran/examples/hyperslabtest/hyperslabtest.vfproj
Commit message (Collapse)AuthorAgeFilesLines
* [svn-r22953] Purpose:Dana Robinson2012-10-231-45/+0
| | | | | Removed legacy Visual Studio solutions and projects, which will no longer be supported after HDF5 1.8.10.
* [svn-r15093] Purpose: Cleanup Windows project files-- remove ignored system ↵Scott Wegner2008-05-291-16/+16
| | | | | | | | | | | library Description: 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. Per a user's suggestion, we remove the ignored library from the project files. This actually makes no difference in the output binaries. Tested: VS2005 on WinXP VS.NET on WinXP
* [svn-r14903] Undoing change committed in r14902.Scot Breitenfeld2008-04-301-20/+20
|
* [svn-r14902] Merged fortran_1_8 branch changes r14505:14901 into the trunk. ↵Scot Breitenfeld2008-04-301-20/+20
| | | | New fortran wrappers added.
* [svn-r14841] Purpose: Fix Windows Fortran examples runtime librariesScott Wegner2008-04-141-20/+20
| | | | | | | | | | 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. Note that this also needs to be updated in the VS.NET project files-- I will make those changes shortly. Tested: VS2005 on WinXP
* [svn-r14093] Purpose: Convert Windows projects to VS2005 format and support ↵Scott Wegner2007-08-161-8/+27
| | | | | | | | | | | 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
* [svn-r14057] Purpose: Fixes for 64-bit Windows Intel Fortran 9.1Scott Wegner2007-08-091-4/+4
| | | | | | | | | | | | 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
* [svn-r13922] Purpose: First step in VS6 DepreciationScott Wegner2007-06-271-0/+26
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