luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-12-28 00:16:15 +01:00
Code Issues Packages Projects Releases Wiki Activity
b14b09c8bc
glib/build/win32/vs10/gio.vcxprojin

220 lines
12 KiB
Plaintext
Raw Normal View History

Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<ItemGroup Label="ProjectConfigurations">
<ProjectConfiguration Include="Debug|Win32">
<Configuration>Debug</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="Debug|x64">
<Configuration>Debug</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="Release|Win32">
<Configuration>Release</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="Release|x64">
<Configuration>Release</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
</ItemGroup>
<PropertyGroup Label="Globals">
<ProjectGuid>{F3D1583C-5613-4809-BD98-7CC1C1276F92}</ProjectGuid>
<RootNamespace>gio</RootNamespace>
</PropertyGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
<WholeProgramOptimization>true</WholeProgramOptimization>
Visual C++ 2010 projects: Prepare support for VS2012 Add the PlatformToolset tag to the project configs so that we can use add a simple script later to the autotools files to copy the projects and change the value (v100 -> v110) of that tag (and other simple changes) in order that we can quickly provide and maintain support for Visual Studio 2012 with minimal effort. Note that at the moment GLib does not yet support the API/SDK requirements for Windows 8 Modern UI (formerly known as Metro), but this paves the very initial step.
2012-11-05 05:31:44 +01:00
<PlatformToolset>v100</PlatformToolset>
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
Visual C++ 2010 projects: Prepare support for VS2012 Add the PlatformToolset tag to the project configs so that we can use add a simple script later to the autotools files to copy the projects and change the value (v100 -> v110) of that tag (and other simple changes) in order that we can quickly provide and maintain support for Visual Studio 2012 with minimal effort. Note that at the moment GLib does not yet support the API/SDK requirements for Windows 8 Modern UI (formerly known as Metro), but this paves the very initial step.
2012-11-05 05:31:44 +01:00
<PlatformToolset>v100</PlatformToolset>
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
<WholeProgramOptimization>true</WholeProgramOptimization>
Visual C++ 2010 projects: Prepare support for VS2012 Add the PlatformToolset tag to the project configs so that we can use add a simple script later to the autotools files to copy the projects and change the value (v100 -> v110) of that tag (and other simple changes) in order that we can quickly provide and maintain support for Visual Studio 2012 with minimal effort. Note that at the moment GLib does not yet support the API/SDK requirements for Windows 8 Modern UI (formerly known as Metro), but this paves the very initial step.
2012-11-05 05:31:44 +01:00
<PlatformToolset>v100</PlatformToolset>
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'" Label="Configuration">
<ConfigurationType>DynamicLibrary</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
Visual C++ 2010 projects: Prepare support for VS2012 Add the PlatformToolset tag to the project configs so that we can use add a simple script later to the autotools files to copy the projects and change the value (v100 -> v110) of that tag (and other simple changes) in order that we can quickly provide and maintain support for Visual Studio 2012 with minimal effort. Note that at the moment GLib does not yet support the API/SDK requirements for Windows 8 Modern UI (formerly known as Metro), but this paves the very initial step.
2012-11-05 05:31:44 +01:00
<PlatformToolset>v100</PlatformToolset>
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
</PropertyGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.props" />
<ImportGroup Label="ExtensionSettings">
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
Visual Studio Projects: Cleanup Property Sheets Make the projects include a single property sheet as necessary, which will in turn include the other property sheet(s) as needed, so that we can avoid warnings where we include the same property sheets twice in a single project. Also make the copying of pre-configured headers into custom build rules so that they can be removed upon the clean command from the IDE and that they can be re-copied if their counterpart *.h.win32 are updated.
2013-12-27 05:25:18 +01:00
<Import Project="glib-gen-srcs.props" />
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
Visual Studio Projects: Cleanup Property Sheets Make the projects include a single property sheet as necessary, which will in turn include the other property sheet(s) as needed, so that we can avoid warnings where we include the same property sheets twice in a single project. Also make the copying of pre-configured headers into custom build rules so that they can be removed upon the clean command from the IDE and that they can be re-copied if their counterpart *.h.win32 are updated.
2013-12-27 05:25:18 +01:00
<Import Project="glib-gen-srcs.props" />
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
Visual Studio Projects: Cleanup Property Sheets Make the projects include a single property sheet as necessary, which will in turn include the other property sheet(s) as needed, so that we can avoid warnings where we include the same property sheets twice in a single project. Also make the copying of pre-configured headers into custom build rules so that they can be removed upon the clean command from the IDE and that they can be re-copied if their counterpart *.h.win32 are updated.
2013-12-27 05:25:18 +01:00
<Import Project="glib-gen-srcs.props" />
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
Visual Studio Projects: Cleanup Property Sheets Make the projects include a single property sheet as necessary, which will in turn include the other property sheet(s) as needed, so that we can avoid warnings where we include the same property sheets twice in a single project. Also make the copying of pre-configured headers into custom build rules so that they can be removed upon the clean command from the IDE and that they can be re-copied if their counterpart *.h.win32 are updated.
2013-12-27 05:25:18 +01:00
<Import Project="glib-gen-srcs.props" />
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
</ImportGroup>
<PropertyGroup Label="UserMacros" />
<PropertyGroup>
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</LinkIncremental>
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">false</LinkIncremental>
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</LinkIncremental>
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='Release|x64'">false</LinkIncremental>
</PropertyGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>../../../gio;../../../gmodule;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
MSVC 2010 Project Files: Split up the Property Sheets Like the Visual Studio 2008 project files, split up the property sheets so to ease maintenace, and to prepare to use autotools to fill in the header entries to "install". Put some of the items that are frequently repeated in the projects as well, also to simplify maintenance. Also, update the autotools files to automate the upgrade of Visual Studio 2010 project as we now have multiple property sheets to copy and process.
2013-08-21 10:57:11 +02:00
<PreprocessorDefinitions>_DEBUG;$(GioBuildDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>EditAndContinue</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
MSVC Builds: GIO: Standardize zlib Linking Link to zlib1.lib for all builds, as: -The notion of zlib1d.lib is rather not standardized across the board for most cases. -Easier for the grand all-in-one solution file.
2015-03-03 11:24:08 +01:00
<AdditionalDependencies>zlib1.lib;$(WindowsNetworkingLibs);%(AdditionalDependencies)</AdditionalDependencies>
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
<OutputFile>$(OutDir)$(GlibDllPrefix)$(ProjectName)$(GlibDllSuffix).dll</OutputFile>
<GenerateDebugInformation>true</GenerateDebugInformation>
MSVC Builds: Few More Enahncements Update the .pdb file generation for the MSVC 2010+ DLLs (and the x64 gspawn helper programs), so that they match the names of the DLLs/EXEs that are built. Also update the .lib generation so that all will use -$(ApiVersion) from the property sheets instead of the -2.0 which was previously hard coded (as we will eventually move into GLib 3.x in the future, for example)
2015-03-04 13:11:43 +01:00
<ProgramDatabaseFile>$(OutDir)$(GlibDllPrefix)$(ProjectName)$(GlibDllSuffix).pdb</ProgramDatabaseFile>
MSVC 2010+ builds: Explicitly use /LTCG The Visual Studio projects used a default setting for link-time code generation, which is a part of the various linker optimizations that is available, which is set as /LTCG for Visual Studio 2013 and earlier. This changed in Visual Studio 2015 to become /LTCG:incremental, which would cause GResources-generated code to be optimized out during linking, unless they were referred to directly in the main line code (such as when the GResource is manually registered), causing programs to crash as a result as they can't find the needed code/data at run time. Fix this by explicitly setting /LTCG for all release builds, for Visual Studio 2010 and later. https://bugzilla.gnome.org/show_bug.cgi?id=752837
2015-10-13 13:30:22 +02:00
<ImportLibrary>$(TargetDir)$(ProjectName)-$(ApiVersion).lib</ImportLibrary>
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
<SubSystem>Windows</SubSystem>
<RandomizedBaseAddress>false</RandomizedBaseAddress>
<DataExecutionPrevention>
</DataExecutionPrevention>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">
<ClCompile>
<AdditionalIncludeDirectories>../../../gio;../../../gmodule;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
MSVC 2010 Project Files: Split up the Property Sheets Like the Visual Studio 2008 project files, split up the property sheets so to ease maintenace, and to prepare to use autotools to fill in the header entries to "install". Put some of the items that are frequently repeated in the projects as well, also to simplify maintenance. Also, update the autotools files to automate the upgrade of Visual Studio 2010 project as we now have multiple property sheets to copy and process.
2013-08-21 10:57:11 +02:00
<PreprocessorDefinitions>$(GioBuildDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
MSVC 2010 Project Files: Split up the Property Sheets Like the Visual Studio 2008 project files, split up the property sheets so to ease maintenace, and to prepare to use autotools to fill in the header entries to "install". Put some of the items that are frequently repeated in the projects as well, also to simplify maintenance. Also, update the autotools files to automate the upgrade of Visual Studio 2010 project as we now have multiple property sheets to copy and process.
2013-08-21 10:57:11 +02:00
<AdditionalDependencies>zlib1.lib;$(WindowsNetworkingLibs);%(AdditionalDependencies)</AdditionalDependencies>
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
<OutputFile>$(OutDir)$(GlibDllPrefix)$(ProjectName)$(GlibDllSuffix).dll</OutputFile>
<GenerateDebugInformation>true</GenerateDebugInformation>
MSVC Builds: Few More Enahncements Update the .pdb file generation for the MSVC 2010+ DLLs (and the x64 gspawn helper programs), so that they match the names of the DLLs/EXEs that are built. Also update the .lib generation so that all will use -$(ApiVersion) from the property sheets instead of the -2.0 which was previously hard coded (as we will eventually move into GLib 3.x in the future, for example)
2015-03-04 13:11:43 +01:00
<ProgramDatabaseFile>$(OutDir)$(GlibDllPrefix)$(ProjectName)$(GlibDllSuffix).pdb</ProgramDatabaseFile>
MSVC 2010+ builds: Explicitly use /LTCG The Visual Studio projects used a default setting for link-time code generation, which is a part of the various linker optimizations that is available, which is set as /LTCG for Visual Studio 2013 and earlier. This changed in Visual Studio 2015 to become /LTCG:incremental, which would cause GResources-generated code to be optimized out during linking, unless they were referred to directly in the main line code (such as when the GResource is manually registered), causing programs to crash as a result as they can't find the needed code/data at run time. Fix this by explicitly setting /LTCG for all release builds, for Visual Studio 2010 and later. https://bugzilla.gnome.org/show_bug.cgi?id=752837
2015-10-13 13:30:22 +02:00
<ImportLibrary>$(TargetDir)$(ProjectName)-$(ApiVersion).lib</ImportLibrary>
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
<SubSystem>Windows</SubSystem>
<OptimizeReferences>true</OptimizeReferences>
<EnableCOMDATFolding>true</EnableCOMDATFolding>
<RandomizedBaseAddress>false</RandomizedBaseAddress>
<DataExecutionPrevention>
</DataExecutionPrevention>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">
<ClCompile>
<Optimization>Disabled</Optimization>
<AdditionalIncludeDirectories>../../../gio;../../../gmodule;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
MSVC 2010 Project Files: Split up the Property Sheets Like the Visual Studio 2008 project files, split up the property sheets so to ease maintenace, and to prepare to use autotools to fill in the header entries to "install". Put some of the items that are frequently repeated in the projects as well, also to simplify maintenance. Also, update the autotools files to automate the upgrade of Visual Studio 2010 project as we now have multiple property sheets to copy and process.
2013-08-21 10:57:11 +02:00
<PreprocessorDefinitions>_DEBUG;$(GioBuildDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
MSVC Builds: GIO: Standardize zlib Linking Link to zlib1.lib for all builds, as: -The notion of zlib1d.lib is rather not standardized across the board for most cases. -Easier for the grand all-in-one solution file.
2015-03-03 11:24:08 +01:00
<AdditionalDependencies>zlib1.lib;$(WindowsNetworkingLibs);%(AdditionalDependencies)</AdditionalDependencies>
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
<OutputFile>$(OutDir)$(GlibDllPrefix)$(ProjectName)$(GlibDllSuffix).dll</OutputFile>
<GenerateDebugInformation>true</GenerateDebugInformation>
MSVC Builds: Few More Enahncements Update the .pdb file generation for the MSVC 2010+ DLLs (and the x64 gspawn helper programs), so that they match the names of the DLLs/EXEs that are built. Also update the .lib generation so that all will use -$(ApiVersion) from the property sheets instead of the -2.0 which was previously hard coded (as we will eventually move into GLib 3.x in the future, for example)
2015-03-04 13:11:43 +01:00
<ProgramDatabaseFile>$(OutDir)$(GlibDllPrefix)$(ProjectName)$(GlibDllSuffix).pdb</ProgramDatabaseFile>
MSVC 2010+ builds: Explicitly use /LTCG The Visual Studio projects used a default setting for link-time code generation, which is a part of the various linker optimizations that is available, which is set as /LTCG for Visual Studio 2013 and earlier. This changed in Visual Studio 2015 to become /LTCG:incremental, which would cause GResources-generated code to be optimized out during linking, unless they were referred to directly in the main line code (such as when the GResource is manually registered), causing programs to crash as a result as they can't find the needed code/data at run time. Fix this by explicitly setting /LTCG for all release builds, for Visual Studio 2010 and later. https://bugzilla.gnome.org/show_bug.cgi?id=752837
2015-10-13 13:30:22 +02:00
<ImportLibrary>$(TargetDir)$(ProjectName)-$(ApiVersion).lib</ImportLibrary>
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
<SubSystem>Windows</SubSystem>
<RandomizedBaseAddress>false</RandomizedBaseAddress>
<DataExecutionPrevention>
</DataExecutionPrevention>
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'">
<ClCompile>
<AdditionalIncludeDirectories>../../../gio;../../../gmodule;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
MSVC 2010 Project Files: Split up the Property Sheets Like the Visual Studio 2008 project files, split up the property sheets so to ease maintenace, and to prepare to use autotools to fill in the header entries to "install". Put some of the items that are frequently repeated in the projects as well, also to simplify maintenance. Also, update the autotools files to automate the upgrade of Visual Studio 2010 project as we now have multiple property sheets to copy and process.
2013-08-21 10:57:11 +02:00
<PreprocessorDefinitions>$(GioBuildDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
MSVC 2010 Project Files: Split up the Property Sheets Like the Visual Studio 2008 project files, split up the property sheets so to ease maintenace, and to prepare to use autotools to fill in the header entries to "install". Put some of the items that are frequently repeated in the projects as well, also to simplify maintenance. Also, update the autotools files to automate the upgrade of Visual Studio 2010 project as we now have multiple property sheets to copy and process.
2013-08-21 10:57:11 +02:00
<AdditionalDependencies>zlib1.lib;$(WindowsNetworkingLibs);%(AdditionalDependencies)</AdditionalDependencies>
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
<OutputFile>$(OutDir)$(GlibDllPrefix)$(ProjectName)$(GlibDllSuffix).dll</OutputFile>
<GenerateDebugInformation>true</GenerateDebugInformation>
MSVC Builds: Few More Enahncements Update the .pdb file generation for the MSVC 2010+ DLLs (and the x64 gspawn helper programs), so that they match the names of the DLLs/EXEs that are built. Also update the .lib generation so that all will use -$(ApiVersion) from the property sheets instead of the -2.0 which was previously hard coded (as we will eventually move into GLib 3.x in the future, for example)
2015-03-04 13:11:43 +01:00
<ProgramDatabaseFile>$(OutDir)$(GlibDllPrefix)$(ProjectName)$(GlibDllSuffix).pdb</ProgramDatabaseFile>
MSVC 2010+ builds: Explicitly use /LTCG The Visual Studio projects used a default setting for link-time code generation, which is a part of the various linker optimizations that is available, which is set as /LTCG for Visual Studio 2013 and earlier. This changed in Visual Studio 2015 to become /LTCG:incremental, which would cause GResources-generated code to be optimized out during linking, unless they were referred to directly in the main line code (such as when the GResource is manually registered), causing programs to crash as a result as they can't find the needed code/data at run time. Fix this by explicitly setting /LTCG for all release builds, for Visual Studio 2010 and later. https://bugzilla.gnome.org/show_bug.cgi?id=752837
2015-10-13 13:30:22 +02:00
<ImportLibrary>$(TargetDir)$(ProjectName)-$(ApiVersion).lib</ImportLibrary>
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
<SubSystem>Windows</SubSystem>
<OptimizeReferences>true</OptimizeReferences>
<EnableCOMDATFolding>true</EnableCOMDATFolding>
<RandomizedBaseAddress>false</RandomizedBaseAddress>
<DataExecutionPrevention>
</DataExecutionPrevention>
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemGroup>
Cleanup and Enhance the MSVC Project Generation Make use of the common autotools module that is used to generate the MSVC project files from their respective templates so that the main build files beccome cleaner, and enhance them in a way that the headers that should be installed can be written to the property sheets during 'make dist', so that the chances of missing headers for MSVC builds can be greatly reduced. Also use this autotools module to fill in the projects for glib-compile-schemas and glib-compile-resources. https://bugzilla.gnome.org/show_bug.cgi?id=735429
2015-09-03 09:19:48 +02:00
#include "gio.vs10.sourcefiles"
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
</ItemGroup>
Visual Studio Projects: Cleanup Property Sheets Make the projects include a single property sheet as necessary, which will in turn include the other property sheet(s) as needed, so that we can avoid warnings where we include the same property sheets twice in a single project. Also make the copying of pre-configured headers into custom build rules so that they can be removed upon the clean command from the IDE and that they can be re-copied if their counterpart *.h.win32 are updated.
2013-12-27 05:25:18 +01:00
<ItemGroup>
<CustomBuild Include="..\..\..\gio\gnetworking.h.win32">
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">Copying gnetworking.h from gnetworking.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">$(GenGNetworkingH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">..\..\..\gio\gnetworking.h;%(Outputs)</Outputs>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">Copying gnetworking.h from gnetworking.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(GenGNetworkingH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">..\..\..\gio\gnetworking.h;%(Outputs)</Outputs>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">Copying gnetworking.h from gnetworking.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">$(GenGNetworkingH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">..\..\..\gio\gnetworking.h;%(Outputs)</Outputs>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">Copying gnetworking.h from gnetworking.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(GenGNetworkingH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">..\..\..\gio\gnetworking.h;%(Outputs)</Outputs>
</CustomBuild>
</ItemGroup>
Update GIO VS 2010 project templates Revert EOL of these files to Unix style as they are to be processed during "make dist"
2011-07-04 16:21:05 +02:00
<ItemGroup>
<ResourceCompile Include="..\..\..\gio\gio.rc" />
</ItemGroup>
<ItemGroup>
<ProjectReference Include="glib.vcxproj">
<Project>{12bca020-eabf-429e-876a-a476bc9c10c0}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
<ProjectReference Include="gmodule.vcxproj">
<Project>{4214047c-f5c1-40b3-8369-5dced8c32770}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
<ProjectReference Include="gobject.vcxproj">
<Project>{f172effc-e30f-4593-809e-db2024b1e753}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
</ItemGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
<ImportGroup Label="ExtensionTargets">
</ImportGroup>
Cleanup and Enhance the MSVC Project Generation Make use of the common autotools module that is used to generate the MSVC project files from their respective templates so that the main build files beccome cleaner, and enhance them in a way that the headers that should be installed can be written to the property sheets during 'make dist', so that the chances of missing headers for MSVC builds can be greatly reduced. Also use this autotools module to fill in the projects for glib-compile-schemas and glib-compile-resources. https://bugzilla.gnome.org/show_bug.cgi?id=735429
2015-09-03 09:19:48 +02:00
</Project>
Reference in New Issue Copy Permalink