luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-11-14 13:26:16 +01:00
Code Issues Packages Projects Releases Wiki Activity
3c0cddfe80
glib/build/win32/vs10/glib.vcxprojin

662 lines
58 KiB
Plaintext
Raw Normal View History

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
<?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>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<ProjectConfiguration Include="Debug_BundledPCRE|Win32">
<Configuration>Debug_BundledPCRE</Configuration>
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
<Platform>Win32</Platform>
</ProjectConfiguration>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<ProjectConfiguration Include="Debug_BundledPCRE|x64">
<Configuration>Debug_BundledPCRE</Configuration>
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
<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>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<ProjectConfiguration Include="Release_BundledPCRE|Win32">
<Configuration>Release_BundledPCRE</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="Release_BundledPCRE|x64">
<Configuration>Release_BundledPCRE</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
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
</ItemGroup>
<PropertyGroup Label="Globals">
<ProjectGuid>{12BCA020-EABF-429E-876A-A476BC9C10C0}</ProjectGuid>
<RootNamespace>glib</RootNamespace>
<Keyword>Win32Proj</Keyword>
</PropertyGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'" Label="Configuration">
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
<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>
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
</PropertyGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'" Label="Configuration">
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
<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>
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
</PropertyGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'" Label="Configuration">
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
<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>
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
</PropertyGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'" Label="Configuration">
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
<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>
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
</PropertyGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'" Label="Configuration">
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
<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>
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
</PropertyGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'" Label="Configuration">
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
<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>
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
</PropertyGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'" Label="Configuration">
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
<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>
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
</PropertyGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'" Label="Configuration">
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
<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>
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
</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" />
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
</ImportGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'" Label="PropertySheets">
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
<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" />
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
</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" />
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
</ImportGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'" Label="PropertySheets">
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
<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" />
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
</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" />
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
</ImportGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'" Label="PropertySheets">
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
<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" />
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
</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" />
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
</ImportGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
<Import Project="glib-gen-srcs.props" />
</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
<PropertyGroup Label="UserMacros" />
<PropertyGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">true</LinkIncremental>
<OutDir Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">Debug\$(Platform)\bin\</OutDir>
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
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</LinkIncremental>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">true</LinkIncremental>
<OutDir Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">Debug\$(Platform)\bin\</OutDir>
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
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</LinkIncremental>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">false</LinkIncremental>
<OutDir Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">Release\$(Platform)\bin\</OutDir>
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
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">false</LinkIncremental>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">false</LinkIncremental>
<OutDir Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">Release\$(Platform)\bin\</OutDir>
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
<LinkIncremental Condition="'$(Configuration)|$(Platform)'=='Release|x64'">false</LinkIncremental>
</PropertyGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">
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
<ClCompile>
<Optimization>Disabled</Optimization>
Tidy Up the glib MSVC Project Move the per-source define/undefine cflags into the property sheets, and apply the cflags for the bundled PCRE sources to the PCRE sources only
2014-01-06 05:21:46 +01:00
<PreprocessorDefinitions>_DEBUG;$(GLibBuildDefines);G_ENABLE_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
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
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>EditAndContinue</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
Update GLib Visual C++ projects Also link to WinMM.lib since timeGetTime is used (commit 8d023c27).
2011-11-21 03:45:27 +01:00
<AdditionalDependencies>ws2_32.lib;winmm.lib;%(AdditionalDependencies)</AdditionalDependencies>
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
<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>
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
<SubSystem>Windows</SubSystem>
<RandomizedBaseAddress>false</RandomizedBaseAddress>
<DataExecutionPrevention>
</DataExecutionPrevention>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">
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
<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;$(GLibBuildDefines);G_ENABLE_DEBUG;$(UseSystemPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
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
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>EditAndContinue</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
Update GLib Visual C++ projects Also link to WinMM.lib since timeGetTime is used (commit 8d023c27).
2011-11-21 03:45:27 +01:00
<AdditionalDependencies>ws2_32.lib;winmm.lib;pcred.lib;%(AdditionalDependencies)</AdditionalDependencies>
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
<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>
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
<SubSystem>Windows</SubSystem>
<RandomizedBaseAddress>false</RandomizedBaseAddress>
<DataExecutionPrevention>
</DataExecutionPrevention>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">
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
<ClCompile>
<Optimization>Disabled</Optimization>
Tidy Up the glib MSVC Project Move the per-source define/undefine cflags into the property sheets, and apply the cflags for the bundled PCRE sources to the PCRE sources only
2014-01-06 05:21:46 +01:00
<PreprocessorDefinitions>_DEBUG;$(GLibBuildDefines);G_ENABLE_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
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
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
Update GLib Visual C++ projects Also link to WinMM.lib since timeGetTime is used (commit 8d023c27).
2011-11-21 03:45:27 +01:00
<AdditionalDependencies>ws2_32.lib;winmm.lib;%(AdditionalDependencies)</AdditionalDependencies>
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
<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>
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
<SubSystem>Windows</SubSystem>
<RandomizedBaseAddress>false</RandomizedBaseAddress>
<DataExecutionPrevention>
</DataExecutionPrevention>
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">
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
<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;$(GLibBuildDefines);G_ENABLE_DEBUG;$(UseSystemPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
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
<MinimalRebuild>true</MinimalRebuild>
<BasicRuntimeChecks>EnableFastChecks</BasicRuntimeChecks>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
Update GLib Visual C++ projects Also link to WinMM.lib since timeGetTime is used (commit 8d023c27).
2011-11-21 03:45:27 +01:00
<AdditionalDependencies>ws2_32.lib;winmm.lib;pcred.lib;%(AdditionalDependencies)</AdditionalDependencies>
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
<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>
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
<SubSystem>Windows</SubSystem>
<RandomizedBaseAddress>false</RandomizedBaseAddress>
<DataExecutionPrevention>
</DataExecutionPrevention>
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">
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
<ClCompile>
Tidy Up the glib MSVC Project Move the per-source define/undefine cflags into the property sheets, and apply the cflags for the bundled PCRE sources to the PCRE sources only
2014-01-06 05:21:46 +01:00
<PreprocessorDefinitions>$(GLibBuildDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
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
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
Update GLib Visual C++ projects Also link to WinMM.lib since timeGetTime is used (commit 8d023c27).
2011-11-21 03:45:27 +01:00
<AdditionalDependencies>ws2_32.lib;winmm.lib;%(AdditionalDependencies)</AdditionalDependencies>
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
<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>
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
<SubSystem>Windows</SubSystem>
<OptimizeReferences>true</OptimizeReferences>
<EnableCOMDATFolding>true</EnableCOMDATFolding>
<RandomizedBaseAddress>false</RandomizedBaseAddress>
<DataExecutionPrevention>
</DataExecutionPrevention>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">
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
<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>$(GLibBuildDefines);$(UseSystemPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
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
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
Update GLib Visual C++ projects Also link to WinMM.lib since timeGetTime is used (commit 8d023c27).
2011-11-21 03:45:27 +01:00
<AdditionalDependencies>ws2_32.lib;winmm.lib;pcre.lib;%(AdditionalDependencies)</AdditionalDependencies>
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
<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>
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
<SubSystem>Windows</SubSystem>
<OptimizeReferences>true</OptimizeReferences>
<EnableCOMDATFolding>true</EnableCOMDATFolding>
<RandomizedBaseAddress>false</RandomizedBaseAddress>
<DataExecutionPrevention>
</DataExecutionPrevention>
<TargetMachine>MachineX86</TargetMachine>
</Link>
</ItemDefinitionGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">
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
<ClCompile>
Tidy Up the glib MSVC Project Move the per-source define/undefine cflags into the property sheets, and apply the cflags for the bundled PCRE sources to the PCRE sources only
2014-01-06 05:21:46 +01:00
<PreprocessorDefinitions>$(GLibBuildDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
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
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
Update GLib Visual C++ projects Also link to WinMM.lib since timeGetTime is used (commit 8d023c27).
2011-11-21 03:45:27 +01:00
<AdditionalDependencies>ws2_32.lib;winmm.lib;%(AdditionalDependencies)</AdditionalDependencies>
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
<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>
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
<SubSystem>Windows</SubSystem>
<OptimizeReferences>true</OptimizeReferences>
<EnableCOMDATFolding>true</EnableCOMDATFolding>
<RandomizedBaseAddress>false</RandomizedBaseAddress>
<DataExecutionPrevention>
</DataExecutionPrevention>
<TargetMachine>MachineX64</TargetMachine>
</Link>
</ItemDefinitionGroup>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'">
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
<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>$(GLibBuildDefines);$(UseSystemPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
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
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<PrecompiledHeader>
</PrecompiledHeader>
<WarningLevel>Level3</WarningLevel>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
<CompileAs>CompileAsC</CompileAs>
</ClCompile>
<Link>
Update GLib Visual C++ projects Also link to WinMM.lib since timeGetTime is used (commit 8d023c27).
2011-11-21 03:45:27 +01:00
<AdditionalDependencies>ws2_32.lib;winmm.lib;pcre.lib;%(AdditionalDependencies)</AdditionalDependencies>
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
<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>
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
<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 "glib.vs10.sourcefiles"
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
<ClCompile Include="..\..\..\glib\giowin32.c" />
<ClCompile Include="..\..\..\glib\gspawn-win32.c" />
Fix GLib MSVC Project The glib/gthread-win32.c was accidently removed from the last commit, sorry
2014-01-06 05:31:18 +01:00
<ClCompile Include="..\..\..\glib\gthread-win32.c" />
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
<ClCompile Include="..\..\..\glib\gwin32.c" />
<ClCompile Include="..\..\..\glib\libcharset\localcharset.c">
Tidy Up the glib MSVC Project Move the per-source define/undefine cflags into the property sheets, and apply the cflags for the bundled PCRE sources to the PCRE sources only
2014-01-06 05:21:46 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">$(LocalCharsetDefs);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(LocalCharsetDefs);%(PreprocessorDefinitions)</PreprocessorDefinitions>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(LocalCharsetDefs);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(LocalCharsetDefs);%(PreprocessorDefinitions)</PreprocessorDefinitions>
Tidy Up the glib MSVC Project Move the per-source define/undefine cflags into the property sheets, and apply the cflags for the bundled PCRE sources to the PCRE sources only
2014-01-06 05:21:46 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">$(LocalCharsetDefs);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(LocalCharsetDefs);%(PreprocessorDefinitions)</PreprocessorDefinitions>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(LocalCharsetDefs);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(LocalCharsetDefs);%(PreprocessorDefinitions)</PreprocessorDefinitions>
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
</ClCompile>
<ClCompile Include="..\..\..\glib\gnulib\asnprintf.c" />
<ClCompile Include="..\..\..\glib\gnulib\printf-args.c" />
<ClCompile Include="..\..\..\glib\gnulib\printf-parse.c" />
<ClCompile Include="..\..\..\glib\gnulib\printf.c" />
<ClCompile Include="..\..\..\glib\gnulib\vasnprintf.c" />
Update Visual C++ projects Update the build support of the included PCRE as we are now including PCRE 8.30 with the GLib distribution. Also "install" the new gversionmacros.h header file.
2012-02-29 04:58:16 +01:00
<ClCompile Include="..\..\..\glib\pcre\pcre_byte_order.c">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|x64'">true</ExcludedFromBuild>
Update Visual C++ projects Update the build support of the included PCRE as we are now including PCRE 8.30 with the GLib distribution. Also "install" the new gversionmacros.h header file.
2012-02-29 04:58:16 +01:00
</ClCompile>
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
<ClCompile Include="..\..\..\glib\pcre\pcre_chartables.c">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|x64'">true</ExcludedFromBuild>
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
</ClCompile>
<ClCompile Include="..\..\..\glib\pcre\pcre_compile.c">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|x64'">true</ExcludedFromBuild>
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
</ClCompile>
<ClCompile Include="..\..\..\glib\pcre\pcre_config.c">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|x64'">true</ExcludedFromBuild>
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
</ClCompile>
<ClCompile Include="..\..\..\glib\pcre\pcre_dfa_exec.c">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|x64'">true</ExcludedFromBuild>
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
</ClCompile>
<ClCompile Include="..\..\..\glib\pcre\pcre_exec.c">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|x64'">true</ExcludedFromBuild>
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
</ClCompile>
<ClCompile Include="..\..\..\glib\pcre\pcre_fullinfo.c">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|x64'">true</ExcludedFromBuild>
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
</ClCompile>
<ClCompile Include="..\..\..\glib\pcre\pcre_get.c">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|x64'">true</ExcludedFromBuild>
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
</ClCompile>
<ClCompile Include="..\..\..\glib\pcre\pcre_globals.c">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|x64'">true</ExcludedFromBuild>
Update Visual C++ projects Update the build support of the included PCRE as we are now including PCRE 8.30 with the GLib distribution. Also "install" the new gversionmacros.h header file.
2012-02-29 04:58:16 +01:00
</ClCompile>
<ClCompile Include="..\..\..\glib\pcre\pcre_jit_compile.c">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|x64'">true</ExcludedFromBuild>
Update Visual C++ projects Update the build support of the included PCRE as we are now including PCRE 8.30 with the GLib distribution. Also "install" the new gversionmacros.h header file.
2012-02-29 04:58:16 +01:00
</ClCompile>
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
<ClCompile Include="..\..\..\glib\pcre\pcre_newline.c">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|x64'">true</ExcludedFromBuild>
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
</ClCompile>
<ClCompile Include="..\..\..\glib\pcre\pcre_ord2utf8.c">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|x64'">true</ExcludedFromBuild>
Update Visual C++ projects Update the build support of the included PCRE as we are now including PCRE 8.30 with the GLib distribution. Also "install" the new gversionmacros.h header file.
2012-02-29 04:58:16 +01:00
</ClCompile>
<ClCompile Include="..\..\..\glib\pcre\pcre_string_utils.c">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|x64'">true</ExcludedFromBuild>
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
</ClCompile>
<ClCompile Include="..\..\..\glib\pcre\pcre_study.c">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|x64'">true</ExcludedFromBuild>
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
</ClCompile>
<ClCompile Include="..\..\..\glib\pcre\pcre_tables.c">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|x64'">true</ExcludedFromBuild>
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
</ClCompile>
Update Visual C++ projects Update the build support of the included PCRE as we are now including PCRE 8.30 with the GLib distribution. Also "install" the new gversionmacros.h header file.
2012-02-29 04:58:16 +01:00
<ClCompile Include="..\..\..\glib\pcre\pcre_valid_utf8.c">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|x64'">true</ExcludedFromBuild>
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
</ClCompile>
<ClCompile Include="..\..\..\glib\pcre\pcre_xclass.c">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">true</ExcludedFromBuild>
<PreprocessorDefinitions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREDefines);%(PreprocessorDefinitions)</PreprocessorDefinitions>
<AdditionalOptions Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GLibBundledPCREUndefs) %(AdditionalOptions)</AdditionalOptions>
<ExcludedFromBuild Condition="'$(Configuration)|$(Platform)'=='Release|x64'">true</ExcludedFromBuild>
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
</ClCompile>
</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="..\..\..\config.h.win32">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<Message Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">Copying config.h from config.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GenConfigH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">..\..\..\config.h;%(Outputs)</Outputs>
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
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">Copying config.h from config.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">$(GenConfigH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">..\..\..\config.h;%(Outputs)</Outputs>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<Message Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">Copying config.h from config.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GenConfigH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">..\..\..\config.h;%(Outputs)</Outputs>
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
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">Copying config.h from config.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(GenConfigH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">..\..\..\config.h;%(Outputs)</Outputs>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<Message Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">Copying config.h from config.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GenConfigH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">..\..\..\config.h;%(Outputs)</Outputs>
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
<Message Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">Copying config.h from config.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">$(GenConfigH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">..\..\..\config.h;%(Outputs)</Outputs>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<Message Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">Copying config.h from config.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GenConfigH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">..\..\..\config.h;%(Outputs)</Outputs>
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
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">Copying config.h from config.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(GenConfigH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">..\..\..\config.h;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="..\..\..\glib\glibconfig.h.win32">
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<Message Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">Copying glibconfig.h from glibconfig.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">$(GenGLibConfigH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|Win32'">..\..\..\glib\glibconfig.h;%(Outputs)</Outputs>
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
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">Copying glibconfig.h from glibconfig.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">$(GenGLibConfigH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">..\..\..\glib\glibconfig.h;%(Outputs)</Outputs>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<Message Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">Copying glibconfig.h from glibconfig.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">$(GenGLibConfigH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug_BundledPCRE|x64'">..\..\..\glib\glibconfig.h;%(Outputs)</Outputs>
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
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">Copying glibconfig.h from glibconfig.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(GenGLibConfigH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">..\..\..\glib\glibconfig.h;%(Outputs)</Outputs>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<Message Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">Copying glibconfig.h from glibconfig.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">$(GenGLibConfigH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|Win32'">..\..\..\glib\glibconfig.h;%(Outputs)</Outputs>
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
<Message Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">Copying glibconfig.h from glibconfig.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">$(GenGLibConfigH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">..\..\..\glib\glibconfig.h;%(Outputs)</Outputs>
Visual Studio builds: Rearrange build configs This is a follow-up commit for commit 82c2461, where the default build is to use the PCRE that is installed in the system, if it is available and is not overridden with --with-internal-pcre. For Visual Studio builds, this means that the new 'Debug' and 'Release' configs will now use PCRE that is found on the system, which were renamed from the '*_ExtPCRE' configs; and that there are now 'Debug_BundledPCRE' and 'Release_BundledPCRE' configs which make use of the PCRE that is supplied with the GLib sources, which, replaces the former 'Debug' and 'Release' configs.
2016-01-18 09:04:45 +01:00
<Message Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">Copying glibconfig.h from glibconfig.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">$(GenGLibConfigH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release_BundledPCRE|x64'">..\..\..\glib\glibconfig.h;%(Outputs)</Outputs>
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
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">Copying glibconfig.h from glibconfig.h.win32...</Message>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(GenGLibConfigH)</Command>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">..\..\..\glib\glibconfig.h;%(Outputs)</Outputs>
</CustomBuild>
</ItemGroup>
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
<ItemGroup>
<ResourceCompile Include="..\..\..\glib\glib.rc" />
</ItemGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
<ImportGroup Label="ExtensionTargets">
</ImportGroup>
Tidy Up the glib MSVC Project Move the per-source define/undefine cflags into the property sheets, and apply the cflags for the bundled PCRE sources to the PCRE sources only
2014-01-06 05:21:46 +01:00
</Project>
Reference in New Issue Copy Permalink