isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-11-29 19:40:43 -05:00
Code Issues Packages Projects Releases Wiki Activity
c91621e8c2
mutter/build/win32/vs10/clutter-install.vcxproj

182 lines
10 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>{35B2A4AC-7235-4FC7-995D-469D59195041}</ProjectGuid>
MSVC Builds: Rename "Install" projects Rename the install projects to clutter-install so that it would be easier to use the project file set as a part of a grand solution file, such as one that is used to build the entire Clutter stack.
2015-03-06 05:47:45 -05:00
<RootNamespace>clutterinstall</RootNamespace>
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04:00
</PropertyGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'" Label="Configuration">
<ConfigurationType>Utility</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|Win32'" Label="Configuration">
<ConfigurationType>Utility</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>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'" Label="Configuration">
<ConfigurationType>Utility</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>Utility</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-install.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-install.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-install.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-install.props" />
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04:00
</ImportGroup>
<PropertyGroup Label="UserMacros" />
<PropertyGroup>
<OutDir Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">$(GlibEtcInstallRoot)\</OutDir>
<OutDir Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(GlibEtcInstallRoot)\</OutDir>
<ExtensionsToDeleteOnClean Condition="'$(Configuration)|$(Platform)'=='Debug|x64'" />
<OutDir Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">$(GlibEtcInstallRoot)\</OutDir>
<OutDir Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(GlibEtcInstallRoot)\</OutDir>
<ExtensionsToDeleteOnClean Condition="'$(Configuration)|$(Platform)'=='Release|x64'" />
</PropertyGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">
</ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'">
</ItemDefinitionGroup>
MSVC 2010+ Projects: Update "Installation" Process Currently, due to the way that Visual Studio 2010+ projects are handled, the "install" project does not re-build upon changes to the sources, as it does not believe that its dependencies have changed, although the changed sources are automatically recompiled. This means that if a part or more of the solution does not build, or if the sources need some other fixes or enhancements, the up-to-date build is not copied automatically, which can be misleading. Improve on the situation by forcing the "install" project to trigger its rebuild, so that the updated binaries can be copied. This does trigger an MSBuild warning, but having that warning is way better than not having an up-to-date build, especially during testing and development.
2014-06-09 06:54:58 -04:00
<ItemGroup>
<CustomBuild Include="..\..\..\config.h.win32">
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">Installing Build Results...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">$(ClutterDoInstall)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">$(InstalledDlls);$(InstalledBins);%(Outputs)</Outputs>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">Installing Build Results...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(ClutterDoInstall)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(InstalledDlls);$(InstalledBins);%(Outputs)</Outputs>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">Installing Build Results...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">$(ClutterDoInstall)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">$(InstalledDlls);$(InstalledBins);%(Outputs)</Outputs>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">Installing Build Results...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(ClutterDoInstall)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(InstalledDlls);$(InstalledBins);%(Outputs)</Outputs>
</CustomBuild>
</ItemGroup>
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04:00
<ItemGroup>
<ProjectReference Include="cally-atkcomponent-example.vcxproj">
<Project>{4b2c0ee0-f1bd-499c-acad-260cf14c352e}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
<ProjectReference Include="cally-atkeditabletext-example.vcxproj">
<Project>{2d1ad595-270b-4b38-9475-a269e225c10c}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
<ProjectReference Include="cally-atkevents-example.vcxproj">
<Project>{c8ec4ce0-9c6a-4733-a0dd-477689faf5f4}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
<ProjectReference Include="cally-atktext-example.vcxproj">
<Project>{27ba2900-a28a-4869-b16d-fbe581a12402}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
<ProjectReference Include="cally-clone-example.vcxproj">
<Project>{e77d40d0-19d4-4865-be20-b6da05ba234d}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
<ProjectReference Include="clutter.vcxproj">
<Project>{ea036190-0950-4640-84f9-d459a33b33a8}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
<ProjectReference Include="test-cogl-perf.vcxproj">
<Project>{0da94d83-b64e-40ac-8074-96c2416bbbe8}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
Rename conform/interactive tests VS projects Add a -clutter suffix for their project names to avoid clashes with the COGL test executables
2011-10-20 04:35:38 -04:00
<ProjectReference Include="test-interactive-clutter.vcxproj">
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04:00
<Project>{75f9e5af-040c-448e-96be-c282efffe2d9}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
Visual C++ support update Add Projects to compile the performance test files.
2011-11-15 04:18:51 -05:00
<ProjectReference Include="test-picking-performance.vcxproj">
<Project>{2035d56a-e748-475f-b3d5-c123bf652143}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04:00
<ProjectReference Include="test-picking.vcxproj">
<Project>{f433db3c-1223-489a-ad0c-c64b09f51139}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
<ProjectReference Include="test-random-text.vcxproj">
<Project>{b8849c58-6773-453c-a2e5-00f02ee20b18}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
Visual C++ support update Add Projects to compile the performance test files.
2011-11-15 04:18:51 -05:00
<ProjectReference Include="test-state-hidden-performance.vcxproj">
<Project>{2d60135e-2e37-4f54-a1c5-43bcd5bbba4f}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
<ProjectReference Include="test-state-interactive-performance.vcxproj">
<Project>{011f9197-f986-44bd-a8f2-045c746b1b70}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
<ProjectReference Include="test-state-mini-performance.vcxproj">
<Project>{d4a09850-e35b-4124-a9ff-784ab5bbcd2c}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
<ProjectReference Include="test-state-performance.vcxproj">
<Project>{bee86058-b4bf-4aa5-91bf-e3620538ed5e}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
<ProjectReference Include="test-state-pick-performance.vcxproj">
<Project>{0c1e8e6c-1563-4f95-a994-6366ee992cb3}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
<ProjectReference Include="test-text-perf-performance.vcxproj">
<Project>{8af1ea8e-305b-42c0-919d-12b1843b21a4}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
msvc-support: Recover wrecked branch Recover the branch! :|
2011-09-16 05:25:47 -04:00
<ProjectReference Include="test-text-perf.vcxproj">
<Project>{f072974f-6675-4a79-96ff-0b0deb113aa4}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
<ProjectReference Include="test-text.vcxproj">
<Project>{b0a69c4a-4e54-45e8-b7e4-b8b2d49e30fc}</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