mirror/hdf5
2
0
Fork 0
mirror of https://github.com/HDFGroup/hdf5.git synced 2024-12-27 08:01:04 +08:00
Code Issues Packages Projects Releases Wiki Activity
aec106e324
hdf5/windows/proj/hdf5_fortrandll/hdf5_fortrandll.vfproj

64 lines
8.4 KiB
Plaintext
Raw Normal View History

[svn-r13922] Purpose: First step in VS6 Depreciation 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
2007-06-28 03:13:45 +08:00
<?xml version="1.0" encoding="UTF-8"?>
<VisualStudioProject ProjectType="typeDynamicLibrary" ProjectCreator="Intel Fortran" Keyword="Dll - Converted from CVF" Version="9.10" ProjectIdGuid="{1063E387-0167-411C-85B9-96B043C4BDB3}">
<Platforms>
[svn-r14093] Purpose: Convert Windows projects to VS2005 format and support 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
2007-08-17 02:28:20 +08:00
<Platform Name="Win32"/>
<Platform Name="x64"/></Platforms>
[svn-r13922] Purpose: First step in VS6 Depreciation 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
2007-06-28 03:13:45 +08:00
<Configurations>
[svn-r14903] Undoing change committed in r14902.
2008-05-01 03:51:13 +08:00
<Configuration Name="Debug|Win32" OutputDirectory="..\..\..\proj\$(ProjectName)\$(ConfigurationName)" IntermediateDirectory="$(OutDir)" DeleteExtensionsOnClean="*.obj;*.mod;*.pdb;*.asm;*.map;*.dyn;*.dpi;*.tmp;*.log;*.ilk;*.exe;$(TargetPath)" ConfigurationType="typeDynamicLibrary" Command="$(TargetPath)">
<Tool Name="VFMidlTool" PreprocessorDefinitions="_DEBUG" MkTypLibCompatible="true" SuppressStartupBanner="true" TargetEnvironment="midlTargetWin32" TypeLibraryName="$(OUTDIR)/hdf5_fortrandll.tlb"/>
[svn-r13922] Purpose: First step in VS6 Depreciation 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
2007-06-28 03:13:45 +08:00
<Tool Name="VFPreBuildEventTool"/>
[svn-r14093] Purpose: Convert Windows projects to VS2005 format and support 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
2007-08-17 02:28:20 +08:00
<Tool Name="VFPostBuildEventTool"/>
[svn-r14903] Undoing change committed in r14902.
2008-05-01 03:51:13 +08:00
<Tool Name="VFFortranCompilerTool" AdditionalOptions="/dll" SuppressStartupBanner="true" DebugInformationFormat="debugEnabled" Optimization="optimizeDisabled" AdditionalIncludeDirectories="Debug/" PreprocessorDefinitions="HDF5F90_WINDOWS,BUILD_HDF5_DLL" FPS4Symbols="true" WarnArgMismatch="true" ModulePath="$(INTDIR)/" ObjectFile="$(INTDIR)/" AssemblerListingLocation="$(INTDIR)/" BoundsCheck="true" RuntimeLibrary="rtMultiThreadedDebugDLL" CompileOnly="true"/>
[svn-r14093] Purpose: Convert Windows projects to VS2005 format and support 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
2007-08-17 02:28:20 +08:00
<Tool Name="VFCustomBuildTool"/>
[svn-r14903] Undoing change committed in r14902.
2008-05-01 03:51:13 +08:00
<Tool Name="VFLinkerTool" OutputFile="$(OutDir)\hdf5_fortranddll.dll " LinkIncremental="linkIncrementalYes" SuppressStartupBanner="true" GenerateDebugInformation="true" SubSystem="subSystemWindows" ImportLibrary="$(TargetDir)$(TargetName).lib" LinkDLL="true" AdditionalDependencies="kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib"/>
[svn-r14854] Purpose: Remove many spurious compiler warnings in Visual Studio 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
2008-04-21 22:03:59 +08:00
<Tool Name="VFPreLinkEventTool"/>
[svn-r14903] Undoing change committed in r14902.
2008-05-01 03:51:13 +08:00
<Tool Name="VFResourceCompilerTool" PreprocessorDefinitions="_DEBUG" Culture="rcEnglishUS" ResourceOutputFileName="$(INTDIR)/$(InputName).res"/></Configuration>
[svn-r14093] Purpose: Convert Windows projects to VS2005 format and support 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
2007-08-17 02:28:20 +08:00
<Configuration Name="Release|Win32" OutputDirectory="..\..\..\proj\$(ProjectName)\$(ConfigurationName)" IntermediateDirectory="$(OutDir)" DeleteExtensionsOnClean="*.obj;*.mod;*.pdb;*.asm;*.map;*.dyn;*.dpi;*.tmp;*.log;*.ilk;*.exe;$(TargetPath)" ConfigurationType="typeDynamicLibrary" MustRebuild="true" Command="$(TargetPath)">
<Tool Name="VFMidlTool" SwitchesHaveChanged="true" PreprocessorDefinitions="NDEBUG" MkTypLibCompatible="true" SuppressStartupBanner="true" TargetEnvironment="midlTargetWin32" TypeLibraryName="$(OUTDIR)/hdf5_fortrandll.tlb"/>
<Tool Name="VFPreBuildEventTool"/>
<Tool Name="VFPostBuildEventTool"/>
[svn-r14854] Purpose: Remove many spurious compiler warnings in Visual Studio 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
2008-04-21 22:03:59 +08:00
<Tool Name="VFFortranCompilerTool" SwitchesHaveChanged="true" AdditionalOptions="/dll" SuppressStartupBanner="true" AdditionalIncludeDirectories="Release/" PreprocessorDefinitions="HDF5F90_WINDOWS,BUILD_HDF5_DLL" ModulePath="$(INTDIR)/" ObjectFile="$(INTDIR)/" AssemblerListingLocation="$(INTDIR)/" RuntimeLibrary="rtMultiThreadedDLL" CompileOnly="true"/>
[svn-r14093] Purpose: Convert Windows projects to VS2005 format and support 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
2007-08-17 02:28:20 +08:00
<Tool Name="VFCustomBuildTool"/>
<Tool Name="VFLinkerTool" SwitchesHaveChanged="true" MustRebuild="true" OutputFile="$(OutDir)\hdf5_fortrandll.dll" LinkIncremental="linkIncrementalNo" SuppressStartupBanner="true" SubSystem="subSystemWindows" ImportLibrary="$(TargetDir)$(TargetName).lib" LinkDLL="true" AdditionalDependencies="kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib"/>
[svn-r14854] Purpose: Remove many spurious compiler warnings in Visual Studio 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
2008-04-21 22:03:59 +08:00
<Tool Name="VFPreLinkEventTool"/>
<Tool Name="VFResourceCompilerTool" SwitchesHaveChanged="true" PreprocessorDefinitions="NDEBUG" Culture="rcEnglishUS" ResourceOutputFileName="$(INTDIR)/$(InputName).res"/></Configuration>
[svn-r14093] Purpose: Convert Windows projects to VS2005 format and support 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
2007-08-17 02:28:20 +08:00
<Configuration Name="Debug|x64" OutputDirectory="..\..\..\proj\$(ProjectName)\$(ConfigurationName)" IntermediateDirectory="$(OutDir)" DeleteExtensionsOnClean="*.obj;*.mod;*.pdb;*.asm;*.map;*.dyn;*.dpi;*.tmp;*.log;*.ilk;*.exe;$(TargetPath)" ConfigurationType="typeDynamicLibrary" MustRebuild="true" Command="$(TargetPath)">
<Tool Name="VFMidlTool" SwitchesHaveChanged="true" PreprocessorDefinitions="_DEBUG" MkTypLibCompatible="true" SuppressStartupBanner="true" TypeLibraryName="$(OUTDIR)/hdf5_fortrandll.tlb"/>
<Tool Name="VFPreBuildEventTool"/>
[svn-r14057] Purpose: Fixes for 64-bit Windows Intel Fortran 9.1 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
2007-08-09 22:04:05 +08:00
<Tool Name="VFFortranCompilerTool" SwitchesHaveChanged="true" AdditionalOptions="/dll" SuppressStartupBanner="true" DebugInformationFormat="debugEnabled" Optimization="optimizeDisabled" AdditionalIncludeDirectories="Debug/" PreprocessorDefinitions="HDF5F90_WINDOWS,BUILD_HDF5_DLL" FPS4Symbols="true" WarnArgMismatch="true" ModulePath="$(INTDIR)/" ObjectFile="$(INTDIR)/" AssemblerListingLocation="$(INTDIR)/" BoundsCheck="true" RuntimeLibrary="rtMultiThreadedDebugDLL" CompileOnly="true"/>
[svn-r14854] Purpose: Remove many spurious compiler warnings in Visual Studio 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
2008-04-21 22:03:59 +08:00
<Tool Name="VFPostBuildEventTool"/>
[svn-r13922] Purpose: First step in VS6 Depreciation 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
2007-06-28 03:13:45 +08:00
<Tool Name="VFCustomBuildTool"/>
[svn-r14093] Purpose: Convert Windows projects to VS2005 format and support 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
2007-08-17 02:28:20 +08:00
<Tool Name="VFLinkerTool" SwitchesHaveChanged="true" MustRebuild="true" OutputFile="$(OutDir)\hdf5_fortranddll.dll " LinkIncremental="linkIncrementalYes" SuppressStartupBanner="true" GenerateDebugInformation="true" SubSystem="subSystemWindows" ImportLibrary="$(TargetDir)$(TargetName).lib" LinkDLL="true" AdditionalDependencies="kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib"/>
[svn-r14854] Purpose: Remove many spurious compiler warnings in Visual Studio 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
2008-04-21 22:03:59 +08:00
<Tool Name="VFResourceCompilerTool" SwitchesHaveChanged="true" PreprocessorDefinitions="_DEBUG" Culture="rcEnglishUS" ResourceOutputFileName="$(INTDIR)/$(InputName).res"/>
<Tool Name="VFPreLinkEventTool"/></Configuration>
[svn-r14093] Purpose: Convert Windows projects to VS2005 format and support 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
2007-08-17 02:28:20 +08:00
<Configuration Name="Release|x64" OutputDirectory="..\..\..\proj\$(ProjectName)\$(ConfigurationName)" IntermediateDirectory="$(OutDir)" DeleteExtensionsOnClean="*.obj;*.mod;*.pdb;*.asm;*.map;*.dyn;*.dpi;*.tmp;*.log;*.ilk;*.exe;$(TargetPath)" ConfigurationType="typeDynamicLibrary" MustRebuild="true" Command="$(TargetPath)">
<Tool Name="VFMidlTool" SwitchesHaveChanged="true" PreprocessorDefinitions="NDEBUG" MkTypLibCompatible="true" SuppressStartupBanner="true" TypeLibraryName="$(OUTDIR)/hdf5_fortrandll.tlb"/>
[svn-r13922] Purpose: First step in VS6 Depreciation 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
2007-06-28 03:13:45 +08:00
<Tool Name="VFPreBuildEventTool"/>
[svn-r14057] Purpose: Fixes for 64-bit Windows Intel Fortran 9.1 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
2007-08-09 22:04:05 +08:00
<Tool Name="VFFortranCompilerTool" SwitchesHaveChanged="true" AdditionalOptions="/dll" SuppressStartupBanner="true" AdditionalIncludeDirectories="Release/" PreprocessorDefinitions="HDF5F90_WINDOWS,BUILD_HDF5_DLL" ModulePath="$(INTDIR)/" ObjectFile="$(INTDIR)/" AssemblerListingLocation="$(INTDIR)/" RuntimeLibrary="rtMultiThreadedDLL" CompileOnly="true"/>
[svn-r14854] Purpose: Remove many spurious compiler warnings in Visual Studio 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
2008-04-21 22:03:59 +08:00
<Tool Name="VFPostBuildEventTool"/>
[svn-r13922] Purpose: First step in VS6 Depreciation 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
2007-06-28 03:13:45 +08:00
<Tool Name="VFCustomBuildTool"/>
[svn-r14093] Purpose: Convert Windows projects to VS2005 format and support 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
2007-08-17 02:28:20 +08:00
<Tool Name="VFLinkerTool" SwitchesHaveChanged="true" MustRebuild="true" OutputFile="$(OutDir)\hdf5_fortrandll.dll" LinkIncremental="linkIncrementalNo" SuppressStartupBanner="true" SubSystem="subSystemWindows" ImportLibrary="$(TargetDir)$(TargetName).lib" LinkDLL="true" AdditionalDependencies="kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib"/>
[svn-r14854] Purpose: Remove many spurious compiler warnings in Visual Studio 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
2008-04-21 22:03:59 +08:00
<Tool Name="VFResourceCompilerTool" SwitchesHaveChanged="true" PreprocessorDefinitions="NDEBUG" Culture="rcEnglishUS" ResourceOutputFileName="$(INTDIR)/$(InputName).res"/>
<Tool Name="VFPreLinkEventTool"/></Configuration></Configurations>
[svn-r13922] Purpose: First step in VS6 Depreciation 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
2007-06-28 03:13:45 +08:00
<Files>
<Filter Name="Source Files" Filter="cpp;c;cxx;rc;def;r;odl;idl;hpj;bat;f90;for;f;fpp">
<File RelativePath="..\..\..\fortran\src\H5_ff.f90"/>
<File RelativePath="..\..\..\fortran\src\H5Aff.f90"/>
<File RelativePath="..\..\..\fortran\src\H5Dff.f90"/>
<File RelativePath="..\..\..\fortran\src\H5Eff.f90"/>
<File RelativePath="..\..\..\fortran\src\H5f90global.f90"/>
<File RelativePath="..\..\..\fortran\src\H5Fff.f90"/>
<File RelativePath="..\..\..\fortran\src\H5fortran_flags.f90"/>
<File RelativePath="..\..\..\fortran\src\H5fortran_types.f90"/>
<File RelativePath="..\..\..\fortran\src\H5Gff.f90"/>
<File RelativePath="..\..\..\fortran\src\H5Iff.f90"/>
<File RelativePath="..\..\..\fortran\src\H5Pff.f90"/>
<File RelativePath="..\..\..\fortran\src\H5Rff.f90"/>
<File RelativePath="..\..\..\fortran\src\H5Sff.f90"/>
<File RelativePath="..\..\..\fortran\src\H5Tff.f90"/>
<File RelativePath="..\..\..\fortran\src\H5Zff.f90"/>
<File RelativePath="..\..\..\fortran\src\HDF5.f90"/></Filter>
<Filter Name="Header Files" Filter="h;hpp;hxx;hm;inl;fi;fd"/>
<Filter Name="Resource Files" Filter="ico;cur;bmp;dlg;rc2;rct;bin;rgs;gif;jpg;jpeg;jpe"/></Files>
<Globals/></VisualStudioProject>
Reference in New Issue Copy Permalink