glib/win32/vs9/glib-version-paths.vsprops.in

<?xml version="1.0" encoding="Windows-1252"?>
<VisualStudioPropertySheet
	ProjectType="Visual C++"
	Version="8.00"
	Name="glibversionpathsprops"
	>
	<UserMacro
		Name="VSVer"
		Value="9"
	/>
	<UserMacro
		Name="GlibVersion"
		Value="@GLIB_VERSION@"
	/>
	<UserMacro
		Name="ApiVersion"
		Value="2.0"
	/>
	<UserMacro
		Name="GlibEtcInstallRoot"
		Value="..\..\..\vs$(VSVer)\$(PlatformName)"
	/>
	<UserMacro
		Name="CopyDir"
		Value="$(GlibEtcInstallRoot)"
	/>
	<UserMacro
		Name="GlibDllPrefix"
		Value=""
	/>
	<UserMacro
		Name="GlibDllSuffix"
		Value="-2.0-0"
	/>
	<UserMacro
		Name="PythonDir"
		Value="c:\python27"
	/>
</VisualStudioPropertySheet>
Visual Studio Property Sheets: Use Unix Line Endings This makes it easier to apply patches in the future. 2013-12-27 03:32:01 +01:00			`<?xml version="1.0" encoding="Windows-1252"?>`
			`<VisualStudioPropertySheet`
			`ProjectType="Visual C++"`
			`Version="8.00"`
			`Name="glibversionpathsprops"`
			`>`
			`<UserMacro`
			`Name="VSVer"`
			`Value="9"`
			`/>`
Visual Studio builds: Move @GLIB_VERSION@ usage ... from glib-gen-srcs.[vsprops\|props].in to glib-version-paths.[vsprops\|props].in, and instead let autotools generate glib-version-paths.[vsprops\|props] rather than glib-gen-srcs.[vsprops\|props], as this will need to be referenced for other items as well, namely generating the .pc files which will become useful for introspection builds. 2016-02-25 11:37:01 +01:00			`<UserMacro`
			`Name="GlibVersion"`
			`Value="@GLIB_VERSION@"`
			`/>`
			`<UserMacro`
			`Name="ApiVersion"`
			`Value="2.0"`
			`/>`
Visual Studio Property Sheets: Use Unix Line Endings This makes it easier to apply patches in the future. 2013-12-27 03:32:01 +01:00			`<UserMacro`
			`Name="GlibEtcInstallRoot"`
Visual Studio builds: Move project files to win32/ It was suggested that the project files be moved here as we don't actually need to go two directory layers from $(srcroot), and would help us to standardize on things in the future across the board. 2017-01-09 07:00:46 +01:00			`Value="..\..\..\vs$(VSVer)\$(PlatformName)"`
Visual Studio Property Sheets: Use Unix Line Endings This makes it easier to apply patches in the future. 2013-12-27 03:32:01 +01:00			`/>`
			`<UserMacro`
			`Name="CopyDir"`
			`Value="$(GlibEtcInstallRoot)"`
			`/>`
			`<UserMacro`
			`Name="GlibDllPrefix"`
build: Change DLL naming in Visual Studio projects The previous commit to glib/glibconfig.h.win32.in, though it improves the state of GLib and fixes bugs, cannot be used as a drop-in replacement for code that builds against the previous glib/glibconfig.h(.win32.in) that were build using the Visual Studio projects. Change the DLL names as a result so that the likelihood of problems caused by replacing existing GLib DLLs can be reduced--code that was built against previous GLib MSVC builds should be rebuilt, so that things will work with the newer DLLs, instead of depending on the older DLLs. Note that if Visual Studio builds are done through Meson, existing code that link against GLib should be rebuilt as well, for the same reason. DLLs built with the Visual Studio projects from 2.55.0 onwards should be compatible with the ones that are built with Visual Studio via Meson. 2017-09-15 06:56:40 +02:00			`Value=""`
Visual Studio Property Sheets: Use Unix Line Endings This makes it easier to apply patches in the future. 2013-12-27 03:32:01 +01:00			`/>`
			`<UserMacro`
			`Name="GlibDllSuffix"`
build: Change DLL naming in Visual Studio projects The previous commit to glib/glibconfig.h.win32.in, though it improves the state of GLib and fixes bugs, cannot be used as a drop-in replacement for code that builds against the previous glib/glibconfig.h(.win32.in) that were build using the Visual Studio projects. Change the DLL names as a result so that the likelihood of problems caused by replacing existing GLib DLLs can be reduced--code that was built against previous GLib MSVC builds should be rebuilt, so that things will work with the newer DLLs, instead of depending on the older DLLs. Note that if Visual Studio builds are done through Meson, existing code that link against GLib should be rebuilt as well, for the same reason. DLLs built with the Visual Studio projects from 2.55.0 onwards should be compatible with the ones that are built with Visual Studio via Meson. 2017-09-15 06:56:40 +02:00			`Value="-2.0-0"`
Visual Studio Property Sheets: Use Unix Line Endings This makes it easier to apply patches in the future. 2013-12-27 03:32:01 +01:00			`/>`
MSVC Builds: Generate glib-mkenums If Possible As glib-mkenums would likely be used in the building of the other components of the stack, such as Cogl, Clutter and gsettings-desktop-schemas, generate that using a Python script (if Python can be found) and "install" it. 2014-08-08 11:39:22 +02:00			`<UserMacro`
Visual Studio builds: Use PythonDir instead of PythonPath This is to avoid confusion with the PYTHONPATH envvar that is commonly used to determine where additional Python modules can be loaded, especially in the case of a MSBuild build. Note that envvar names are not case sensitive on Windows in general. 2017-07-13 11:45:44 +02:00			`Name="PythonDir"`
MSVC Builds: Generate glib-mkenums If Possible As glib-mkenums would likely be used in the building of the other components of the stack, such as Cogl, Clutter and gsettings-desktop-schemas, generate that using a Python script (if Python can be found) and "install" it. 2014-08-08 11:39:22 +02:00			`Value="c:\python27"`
			`/>`
Visual Studio Property Sheets: Use Unix Line Endings This makes it easier to apply patches in the future. 2013-12-27 03:32:01 +01:00			`</VisualStudioPropertySheet>`