luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-11-14 21:36:13 +01:00
Code Issues Packages Projects Releases Wiki Activity
feae4e9f31
glib/win32/vs9/glib-install.vcproj

120 lines
3.4 KiB
Plaintext
Raw Normal View History

Visual Studio Projects: Use Unix Line Endings ...where possible, to make application of patches easier in the future. The README.txt's and the .sln files are still in Windows/DOS line endings as they need to be so.
2013-12-27 03:50:35 +01:00
<?xml version="1.0" encoding="Windows-1252"?>
<VisualStudioProject
ProjectType="Visual C++"
Version="9.00"
MSVC Builds: Rename "install" Projects Rename the project to "install" the GLib files, as we are planning to have a grand solution file that would build the entire GTK+ stack with its deps, to ease the process for people building the GTK+ stack from a stock installation of Visual Studio.
2015-02-02 05:49:42 +01:00
Name="glib-install"
Visual Studio Projects: Use Unix Line Endings ...where possible, to make application of patches easier in the future. The README.txt's and the .sln files are still in Windows/DOS line endings as they need to be so.
2013-12-27 03:50:35 +01:00
ProjectGUID="{2093D218-190E-4194-9421-3BA7CBF33B10}"
MSVC Builds: Rename "install" Projects Rename the project to "install" the GLib files, as we are planning to have a grand solution file that would build the entire GTK+ stack with its deps, to ease the process for people building the GTK+ stack from a stock installation of Visual Studio.
2015-02-02 05:49:42 +01:00
RootNamespace="glibinstall"
Visual Studio Projects: Use Unix Line Endings ...where possible, to make application of patches easier in the future. The README.txt's and the .sln files are still in Windows/DOS line endings as they need to be so.
2013-12-27 03:50:35 +01:00
Keyword="Win32Proj"
TargetFrameworkVersion="131072"
>
<Platforms>
<Platform
Name="Win32"
/>
<Platform
Name="x64"
/>
</Platforms>
<ToolFiles>
</ToolFiles>
<Configurations>
<Configuration
Name="Debug|Win32"
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
InheritedPropertySheets=".\glib-install.vsprops"
Visual Studio Projects: Use Unix Line Endings ...where possible, to make application of patches easier in the future. The README.txt's and the .sln files are still in Windows/DOS line endings as they need to be so.
2013-12-27 03:50:35 +01:00
OutputDirectory="$(GlibEtcInstallRoot)"
ConfigurationType="10"
CharacterSet="2"
DeleteExtensionsOnClean=""
>
<Tool
MSVC builds: Add scripts to generate .pc files Add a generic script, pc_base.py, which can be utilized to obtain path info, along with user-input version info, which can be used to generate pkg-config .pc files. Also enhance replace.py a bit so that it can also be used in the future to replace multiple items in a file in one shot. This is done to make building introspection files easier, as it depends much on the pkg-config .pc files to work. Update the project files so that when Python is available, we can generate the full, usable .pc files when we complete and 'install' the builds, and copy them to appropriate locations so that pkg-config can be set to find them easily.
2016-03-10 13:33:35 +01:00
Name="VCPostBuildEventTool"
Visual Studio Projects: Use Unix Line Endings ...where possible, to make application of patches easier in the future. The README.txt's and the .sln files are still in Windows/DOS line endings as they need to be so.
2013-12-27 03:50:35 +01:00
CommandLine="$(GlibDoInstall)"
/>
</Configuration>
<Configuration
Name="Debug|x64"
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
InheritedPropertySheets=".\glib-install.vsprops"
Visual Studio Projects: Use Unix Line Endings ...where possible, to make application of patches easier in the future. The README.txt's and the .sln files are still in Windows/DOS line endings as they need to be so.
2013-12-27 03:50:35 +01:00
OutputDirectory="$(GlibEtcInstallRoot)"
ConfigurationType="10"
CharacterSet="2"
DeleteExtensionsOnClean=""
>
<Tool
MSVC builds: Add scripts to generate .pc files Add a generic script, pc_base.py, which can be utilized to obtain path info, along with user-input version info, which can be used to generate pkg-config .pc files. Also enhance replace.py a bit so that it can also be used in the future to replace multiple items in a file in one shot. This is done to make building introspection files easier, as it depends much on the pkg-config .pc files to work. Update the project files so that when Python is available, we can generate the full, usable .pc files when we complete and 'install' the builds, and copy them to appropriate locations so that pkg-config can be set to find them easily.
2016-03-10 13:33:35 +01:00
Name="VCPostBuildEventTool"
Visual Studio Projects: Use Unix Line Endings ...where possible, to make application of patches easier in the future. The README.txt's and the .sln files are still in Windows/DOS line endings as they need to be so.
2013-12-27 03:50:35 +01:00
CommandLine="$(GlibDoInstall)"
/>
</Configuration>
<Configuration
Name="Release|Win32"
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
InheritedPropertySheets=".\glib-install.vsprops"
Visual Studio Projects: Use Unix Line Endings ...where possible, to make application of patches easier in the future. The README.txt's and the .sln files are still in Windows/DOS line endings as they need to be so.
2013-12-27 03:50:35 +01:00
OutputDirectory="$(GlibEtcInstallRoot)"
ConfigurationType="10"
CharacterSet="2"
WholeProgramOptimization="1"
DeleteExtensionsOnClean=""
>
<Tool
MSVC builds: Add scripts to generate .pc files Add a generic script, pc_base.py, which can be utilized to obtain path info, along with user-input version info, which can be used to generate pkg-config .pc files. Also enhance replace.py a bit so that it can also be used in the future to replace multiple items in a file in one shot. This is done to make building introspection files easier, as it depends much on the pkg-config .pc files to work. Update the project files so that when Python is available, we can generate the full, usable .pc files when we complete and 'install' the builds, and copy them to appropriate locations so that pkg-config can be set to find them easily.
2016-03-10 13:33:35 +01:00
Name="VCPostBuildEventTool"
Visual Studio Projects: Use Unix Line Endings ...where possible, to make application of patches easier in the future. The README.txt's and the .sln files are still in Windows/DOS line endings as they need to be so.
2013-12-27 03:50:35 +01:00
CommandLine="$(GlibDoInstall)"
/>
</Configuration>
<Configuration
Name="Release|x64"
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
InheritedPropertySheets=".\glib-install.vsprops"
Visual Studio Projects: Use Unix Line Endings ...where possible, to make application of patches easier in the future. The README.txt's and the .sln files are still in Windows/DOS line endings as they need to be so.
2013-12-27 03:50:35 +01:00
OutputDirectory="$(GlibEtcInstallRoot)"
ConfigurationType="10"
CharacterSet="2"
WholeProgramOptimization="1"
DeleteExtensionsOnClean=""
>
<Tool
MSVC builds: Add scripts to generate .pc files Add a generic script, pc_base.py, which can be utilized to obtain path info, along with user-input version info, which can be used to generate pkg-config .pc files. Also enhance replace.py a bit so that it can also be used in the future to replace multiple items in a file in one shot. This is done to make building introspection files easier, as it depends much on the pkg-config .pc files to work. Update the project files so that when Python is available, we can generate the full, usable .pc files when we complete and 'install' the builds, and copy them to appropriate locations so that pkg-config can be set to find them easily.
2016-03-10 13:33:35 +01:00
Name="VCPostBuildEventTool"
Visual Studio Projects: Use Unix Line Endings ...where possible, to make application of patches easier in the future. The README.txt's and the .sln files are still in Windows/DOS line endings as they need to be so.
2013-12-27 03:50:35 +01:00
CommandLine="$(GlibDoInstall)"
/>
</Configuration>
</Configurations>
MSVC builds: Add scripts to generate .pc files Add a generic script, pc_base.py, which can be utilized to obtain path info, along with user-input version info, which can be used to generate pkg-config .pc files. Also enhance replace.py a bit so that it can also be used in the future to replace multiple items in a file in one shot. This is done to make building introspection files easier, as it depends much on the pkg-config .pc files to work. Update the project files so that when Python is available, we can generate the full, usable .pc files when we complete and 'install' the builds, and copy them to appropriate locations so that pkg-config can be set to find them easily.
2016-03-10 13:33:35 +01:00
<Files>
<Filter
Name="Resource Files"
Filter="rc;ico;cur;bmp;dlg;rc2;rct;bin;rgs;gif;jpg;jpeg;jpe;resx;tiff;tif;png;wav"
UniqueIdentifier="{67DA6AB6-F800-4c08-8B7A-83BB121AAD01}"
>
<File RelativePath="..\glibpc.py">
<FileConfiguration Name="Debug|Win32">
<Tool
Name="VCCustomBuildTool"
Description="Generating .pc files..."
CommandLine="$(GlibGenPC)"
Outputs="..\gio-windows-2.0.pc;..\gio-2.0.pc;..\gobject-2.0.pc;..\gmodule-no-export-2.0.pc;..\gmodule-export-2.0.pc;..\gmodule-2.0.pc;..\gthread-2.0.pc;..\glib-2.0.pc"
/>
</FileConfiguration>
<FileConfiguration Name="Release|Win32">
<Tool
Name="VCCustomBuildTool"
Description="Generating .pc files..."
CommandLine="$(GlibGenPC)"
Outputs="..\gio-windows-2.0.pc;..\gio-2.0.pc;..\gobject-2.0.pc;..\gmodule-no-export-2.0.pc;..\gmodule-export-2.0.pc;..\gmodule-2.0.pc;..\gthread-2.0.pc;..\glib-2.0.pc"
/>
</FileConfiguration>
<FileConfiguration Name="Debug|x64">
<Tool
Name="VCCustomBuildTool"
Description="Generating .pc files..."
CommandLine="$(GlibGenPC)"
Outputs="..\gio-windows-2.0.pc;..\gio-2.0.pc;..\gobject-2.0.pc;..\gmodule-no-export-2.0.pc;..\gmodule-export-2.0.pc;..\gmodule-2.0.pc;..\gthread-2.0.pc;..\glib-2.0.pc"
/>
</FileConfiguration>
<FileConfiguration Name="Release|x64">
<Tool
Name="VCCustomBuildTool"
Description="Generating .pc files..."
CommandLine="$(GlibGenPC)"
Outputs="..\gio-windows-2.0.pc;..\gio-2.0.pc;..\gobject-2.0.pc;..\gmodule-no-export-2.0.pc;..\gmodule-export-2.0.pc;..\gmodule-2.0.pc;..\gthread-2.0.pc;..\glib-2.0.pc"
/>
</FileConfiguration>
</File>
</Filter>
</Files>
Visual Studio Projects: Use Unix Line Endings ...where possible, to make application of patches easier in the future. The README.txt's and the .sln files are still in Windows/DOS line endings as they need to be so.
2013-12-27 03:50:35 +01:00
</VisualStudioProject>
Reference in New Issue Copy Permalink