luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-11-14 05:16:18 +01:00
Code Issues Packages Projects Releases Wiki Activity
a812e110bf
glib/build/win32/vs10/gspawn-win32-helper-console.vcxproj

175 lines
8.6 KiB
XML
Raw Normal View History

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
<?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>{E40E8A7E-7CAE-4659-9B8B-BC38898E3074}</ProjectGuid>
<RootNamespace>gspawnwin32helperconsole</RootNamespace>
<Keyword>Win32Proj</Keyword>
</PropertyGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'" Label="Configuration">
<ConfigurationType>Application</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
<WholeProgramOptimization>true</WholeProgramOptimization>
<PlatformToolset>v100</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'" Label="Configuration">
<ConfigurationType>Application</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
<PlatformToolset>v100</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'" Label="Configuration">
<ConfigurationType>Application</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
<WholeProgramOptimization>true</WholeProgramOptimization>
<PlatformToolset>v100</PlatformToolset>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'" Label="Configuration">
<ConfigurationType>Application</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
<PlatformToolset>v100</PlatformToolset>
</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" />
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
<Import Project="glib-build-defines.props" />
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
</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" />
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
<Import Project="glib-build-defines.props" />
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
</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" />
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
<Import Project="glib-build-defines.props" />
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
</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" />
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
<Import Project="glib-build-defines.props" />
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
</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>
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;$(GLibInBuildMacro);%(PreprocessorDefinitions)</PreprocessorDefinitions>
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
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>EditAndContinue</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
<GenerateDebugInformation>true</GenerateDebugInformation>
<SubSystem>Console</SubSystem>
<RandomizedBaseAddress>false</RandomizedBaseAddress>
<DataExecutionPrevention>
</DataExecutionPrevention>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">
<ClCompile>
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>$(GLibInBuildMacro);%(PreprocessorDefinitions)</PreprocessorDefinitions>
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
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
<GenerateDebugInformation>true</GenerateDebugInformation>
<SubSystem>Console</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>
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;$(GLibInBuildMacro);%(PreprocessorDefinitions)</PreprocessorDefinitions>
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
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
<OutputFile>$(OutDir)gspawn-win64-helper-console.exe</OutputFile>
<GenerateDebugInformation>true</GenerateDebugInformation>
<SubSystem>Console</SubSystem>
<RandomizedBaseAddress>false</RandomizedBaseAddress>
<DataExecutionPrevention>
</DataExecutionPrevention>
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'">
<ClCompile>
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>$(GLibInBuildMacro);%(PreprocessorDefinitions)</PreprocessorDefinitions>
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
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
<OutputFile>$(OutDir)gspawn-win64-helper-console.exe</OutputFile>
<GenerateDebugInformation>true</GenerateDebugInformation>
<SubSystem>Console</SubSystem>
<OptimizeReferences>true</OptimizeReferences>
<EnableCOMDATFolding>true</EnableCOMDATFolding>
<RandomizedBaseAddress>false</RandomizedBaseAddress>
<DataExecutionPrevention>
</DataExecutionPrevention>
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemGroup>
<ClCompile Include="..\..\..\glib\gspawn-win32-helper-console.c" />
</ItemGroup>
<ItemGroup>
<ProjectReference Include="glib.vcxproj">
<Project>{12bca020-eabf-429e-876a-a476bc9c10c0}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
</ItemGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
<ImportGroup Label="ExtensionTargets">
</ImportGroup>
Visual C++ 2010 Project Files These are the actual GLib VS2010 project files (*.vcxproj, *.vcxproj.filters) and property sheet file (*.props) that are used to compile the GLib, GModule, GObject, GThread, GIO DLLs, along with the gspawn-win32-helper* programs, glib-genmarshal utility and testglib test program. A readme.txt file is also enclosed for references for building GLib under VS2010. Note that the project files for GLib, GIO and GObject are templates that makes use of the autotools items of my last commit so that maintenance of those files are simplified as new source files are added to these rather frequently. Suggestions are welcome for these-please let me know via BugZilla. Thank you!
2011-02-22 13:08:36 +01:00
</Project>
Reference in New Issue Copy Permalink