brl/mutter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
3113f4521b
mutter/build/win32/vs10/test-text-perf.vcxproj

171 lines
8.4 KiB
XML
Raw Normal View History

msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04: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>{F072974F-6675-4A79-96FF-0B0DEB113AA4}</ProjectGuid>
<RootNamespace>testtextperf</RootNamespace>
<Keyword>Win32Proj</Keyword>
</PropertyGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'" Label="Configuration">
<ConfigurationType>Application</ConfigurationType>
Visual C++ projects: Use MultiByte character set Use MultiByte character set for all projects and configs, to avoid any inconsistencies that may arise.
2012-12-16 22:23:59 -05:00
<CharacterSet>MultiByte</CharacterSet>
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04:00
<WholeProgramOptimization>true</WholeProgramOptimization>
Visual Studio 2010 Projects: Add PlatformToolset Tag This adds a PlatformToolset tag for each configuration so that it is easier to upgrade the projects to Visual Studio 2012/2013 formats, which are largely the same as the Visual Studio 2010 projects. We can, for example, use a script to change the values of the PlatformToolset to make these projects usable out-of-the-box for Visual Studio 2012/2013.
2014-03-06 06:51:50 -05:00
<PlatformToolset>v100</PlatformToolset>
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04:00
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'" Label="Configuration">
<ConfigurationType>Application</ConfigurationType>
Visual C++ projects: Use MultiByte character set Use MultiByte character set for all projects and configs, to avoid any inconsistencies that may arise.
2012-12-16 22:23:59 -05:00
<CharacterSet>MultiByte</CharacterSet>
Visual Studio 2010 Projects: Add PlatformToolset Tag This adds a PlatformToolset tag for each configuration so that it is easier to upgrade the projects to Visual Studio 2012/2013 formats, which are largely the same as the Visual Studio 2010 projects. We can, for example, use a script to change the values of the PlatformToolset to make these projects usable out-of-the-box for Visual Studio 2012/2013.
2014-03-06 06:51:50 -05:00
<PlatformToolset>v100</PlatformToolset>
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04:00
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'" Label="Configuration">
<ConfigurationType>Application</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
<WholeProgramOptimization>true</WholeProgramOptimization>
Visual Studio 2010 Projects: Add PlatformToolset Tag This adds a PlatformToolset tag for each configuration so that it is easier to upgrade the projects to Visual Studio 2012/2013 formats, which are largely the same as the Visual Studio 2010 projects. We can, for example, use a script to change the values of the PlatformToolset to make these projects usable out-of-the-box for Visual Studio 2012/2013.
2014-03-06 06:51:50 -05:00
<PlatformToolset>v100</PlatformToolset>
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04:00
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'" Label="Configuration">
<ConfigurationType>Application</ConfigurationType>
<CharacterSet>MultiByte</CharacterSet>
Visual Studio 2010 Projects: Add PlatformToolset Tag This adds a PlatformToolset tag for each configuration so that it is easier to upgrade the projects to Visual Studio 2012/2013 formats, which are largely the same as the Visual Studio 2010 projects. We can, for example, use a script to change the values of the PlatformToolset to make these projects usable out-of-the-box for Visual Studio 2012/2013.
2014-03-06 06:51:50 -05:00
<PlatformToolset>v100</PlatformToolset>
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04: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" />
Overhaul the Visual Studio 2010 Build Files Like the Visual Studio 2008 projects, give the Visual Studio 2010 projects an overhaul, where: -The property sheets are split up, so that they are easier to maintain and each project only needs to include the necessary parts. The various projects are updated accordingly, too. The copying of config.h.win32 and clutter-config.h.win32(_GDK) are now done with custom build rules, so that these files can be cleaned and/or recopied during a clean, rebuild or update. -Clean up the property sheets, to get rid of parts that are actually repeated. Also update the build macros, so that we won't get warnings for repeated #defines of macros and fix the build of the various tests/ demo programs. -Make all projects use Unix line endings, except for the .sln and README.txt files, which need to have Windows line endings. This makes it easier to apply patches to these project files. -Update the installation of headers, as headers are introduced/deprecated. -Cosmetics: get rid of "\ No newline at end of file".
2014-03-06 03:30:30 -05:00
<Import Project="clutter-build-defines.props" />
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04: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" />
Overhaul the Visual Studio 2010 Build Files Like the Visual Studio 2008 projects, give the Visual Studio 2010 projects an overhaul, where: -The property sheets are split up, so that they are easier to maintain and each project only needs to include the necessary parts. The various projects are updated accordingly, too. The copying of config.h.win32 and clutter-config.h.win32(_GDK) are now done with custom build rules, so that these files can be cleaned and/or recopied during a clean, rebuild or update. -Clean up the property sheets, to get rid of parts that are actually repeated. Also update the build macros, so that we won't get warnings for repeated #defines of macros and fix the build of the various tests/ demo programs. -Make all projects use Unix line endings, except for the .sln and README.txt files, which need to have Windows line endings. This makes it easier to apply patches to these project files. -Update the installation of headers, as headers are introduced/deprecated. -Cosmetics: get rid of "\ No newline at end of file".
2014-03-06 03:30:30 -05:00
<Import Project="clutter-build-defines.props" />
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04: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" />
Overhaul the Visual Studio 2010 Build Files Like the Visual Studio 2008 projects, give the Visual Studio 2010 projects an overhaul, where: -The property sheets are split up, so that they are easier to maintain and each project only needs to include the necessary parts. The various projects are updated accordingly, too. The copying of config.h.win32 and clutter-config.h.win32(_GDK) are now done with custom build rules, so that these files can be cleaned and/or recopied during a clean, rebuild or update. -Clean up the property sheets, to get rid of parts that are actually repeated. Also update the build macros, so that we won't get warnings for repeated #defines of macros and fix the build of the various tests/ demo programs. -Make all projects use Unix line endings, except for the .sln and README.txt files, which need to have Windows line endings. This makes it easier to apply patches to these project files. -Update the installation of headers, as headers are introduced/deprecated. -Cosmetics: get rid of "\ No newline at end of file".
2014-03-06 03:30:30 -05:00
<Import Project="clutter-build-defines.props" />
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04: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" />
Overhaul the Visual Studio 2010 Build Files Like the Visual Studio 2008 projects, give the Visual Studio 2010 projects an overhaul, where: -The property sheets are split up, so that they are easier to maintain and each project only needs to include the necessary parts. The various projects are updated accordingly, too. The copying of config.h.win32 and clutter-config.h.win32(_GDK) are now done with custom build rules, so that these files can be cleaned and/or recopied during a clean, rebuild or update. -Clean up the property sheets, to get rid of parts that are actually repeated. Also update the build macros, so that we won't get warnings for repeated #defines of macros and fix the build of the various tests/ demo programs. -Make all projects use Unix line endings, except for the .sln and README.txt files, which need to have Windows line endings. This makes it easier to apply patches to these project files. -Update the installation of headers, as headers are introduced/deprecated. -Cosmetics: get rid of "\ No newline at end of file".
2014-03-06 03:30:30 -05:00
<Import Project="clutter-build-defines.props" />
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04:00
</ImportGroup>
<PropertyGroup Label="UserMacros" />
<PropertyGroup>
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</LinkIncremental>
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</LinkIncremental>
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">false</LinkIncremental>
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='Release|x64'">false</LinkIncremental>
</PropertyGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">
<ClCompile>
<Optimization>Disabled</Optimization>
Visual Studio Builds: Avoid Implicit Linking to SDL Cogl, when built with the SDL winsys, will include the SDL headers when Cogl-based programs are built, which causes the SDL's wrapper for main() to be used on Windows, causing an implicit requirement that all Cogl-based apps must link to SDL2.lib and SDL2main.lib. Avoid this behavior by defining SDL_MAIN_HANDLED in the CFLAGS of the sample and interactive test programs
2014-04-16 22:52:19 -04:00
<PreprocessorDefinitions>_DEBUG;$(BaseWinBuildDef);$(ClutterDisableDeprecationWarnings);$(AvoidSDLMain)%(PreprocessorDefinitions)</PreprocessorDefinitions>
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>EditAndContinue</DebugInformationFormat>
</ClCompile>
<Link>
<GenerateDebugInformation>true</GenerateDebugInformation>
<SubSystem>Console</SubSystem>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">
<ClCompile>
<Optimization>Disabled</Optimization>
Visual Studio Builds: Avoid Implicit Linking to SDL Cogl, when built with the SDL winsys, will include the SDL headers when Cogl-based programs are built, which causes the SDL's wrapper for main() to be used on Windows, causing an implicit requirement that all Cogl-based apps must link to SDL2.lib and SDL2main.lib. Avoid this behavior by defining SDL_MAIN_HANDLED in the CFLAGS of the sample and interactive test programs
2014-04-16 22:52:19 -04:00
<PreprocessorDefinitions>_DEBUG;$(BaseWinBuildDef);$(ClutterDisableDeprecationWarnings);$(AvoidSDLMain)%(PreprocessorDefinitions)</PreprocessorDefinitions>
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04:00
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
<AdditionalDependencies>%(AdditionalDependencies)</AdditionalDependencies>
<GenerateDebugInformation>true</GenerateDebugInformation>
<SubSystem>Console</SubSystem>
<RandomizedBaseAddress>false</RandomizedBaseAddress>
<DataExecutionPrevention>
</DataExecutionPrevention>
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">
<ClCompile>
<Optimization>MaxSpeed</Optimization>
<IntrinsicFunctions>true</IntrinsicFunctions>
Visual Studio Builds: Avoid Implicit Linking to SDL Cogl, when built with the SDL winsys, will include the SDL headers when Cogl-based programs are built, which causes the SDL's wrapper for main() to be used on Windows, causing an implicit requirement that all Cogl-based apps must link to SDL2.lib and SDL2main.lib. Avoid this behavior by defining SDL_MAIN_HANDLED in the CFLAGS of the sample and interactive test programs
2014-04-16 22:52:19 -04:00
<PreprocessorDefinitions>$(BaseWinBuildDef);$(ClutterDisableDeprecationWarnings);$(AvoidSDLMain)%(PreprocessorDefinitions)</PreprocessorDefinitions>
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04:00
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<FunctionLevelLinking>true</FunctionLevelLinking>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
</ClCompile>
<Link>
<GenerateDebugInformation>true</GenerateDebugInformation>
<SubSystem>Console</SubSystem>
<OptimizeReferences>true</OptimizeReferences>
<EnableCOMDATFolding>true</EnableCOMDATFolding>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'">
<ClCompile>
Visual Studio Builds: Avoid Implicit Linking to SDL Cogl, when built with the SDL winsys, will include the SDL headers when Cogl-based programs are built, which causes the SDL's wrapper for main() to be used on Windows, causing an implicit requirement that all Cogl-based apps must link to SDL2.lib and SDL2main.lib. Avoid this behavior by defining SDL_MAIN_HANDLED in the CFLAGS of the sample and interactive test programs
2014-04-16 22:52:19 -04:00
<PreprocessorDefinitions>$(BaseWinBuildDef);$(ClutterDisableDeprecationWarnings);$(AvoidSDLMain)%(PreprocessorDefinitions)</PreprocessorDefinitions>
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04:00
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
<AdditionalDependencies>%(AdditionalDependencies)</AdditionalDependencies>
<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="..\..\..\tests\micro-bench\test-text-perf.c" />
</ItemGroup>
<ItemGroup>
<ProjectReference Include="clutter.vcxproj">
<Project>{ea036190-0950-4640-84f9-d459a33b33a8}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
</ItemGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
<ImportGroup Label="ExtensionTargets">
</ImportGroup>
Overhaul the Visual Studio 2010 Build Files Like the Visual Studio 2008 projects, give the Visual Studio 2010 projects an overhaul, where: -The property sheets are split up, so that they are easier to maintain and each project only needs to include the necessary parts. The various projects are updated accordingly, too. The copying of config.h.win32 and clutter-config.h.win32(_GDK) are now done with custom build rules, so that these files can be cleaned and/or recopied during a clean, rebuild or update. -Clean up the property sheets, to get rid of parts that are actually repeated. Also update the build macros, so that we won't get warnings for repeated #defines of macros and fix the build of the various tests/ demo programs. -Make all projects use Unix line endings, except for the .sln and README.txt files, which need to have Windows line endings. This makes it easier to apply patches to these project files. -Update the installation of headers, as headers are introduced/deprecated. -Cosmetics: get rid of "\ No newline at end of file".
2014-03-06 03:30:30 -05:00
</Project>
Reference in New Issue Copy Permalink