luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-10-31 08:22:16 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
a770239d71bcfede45d92eeac9b49da99da541c3
glib/win32/vs10/glib-version-paths.props.in

47 lines
1.8 KiB
Plaintext
Raw Normal View History

Visual Studio Property Sheets: Use Unix Line Endings This makes it easier to apply patches in the future.
2013-12-27 10:32:01 +08:00
<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup Label="UserMacros">
<VSVer>10</VSVer>
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 18:37:01 +08:00
<GlibVersion>@GLIB_VERSION@</GlibVersion>
<ApiVersion>2.0</ApiVersion>
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 14:00:46 +08:00
<GlibEtcInstallRoot>..\..\..\vs$(VSVer)\$(Platform)</GlibEtcInstallRoot>
Visual Studio Property Sheets: Use Unix Line Endings This makes it easier to apply patches in the future.
2013-12-27 10:32:01 +08:00
<CopyDir>$(GlibEtcInstallRoot)</CopyDir>
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 12:56:40 +08:00
<GlibDllPrefix></GlibDllPrefix>
<GlibDllSuffix>-2.0-0</GlibDllSuffix>
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 17:45:44 +08:00
<PythonDir Condition="'$(VisualStudioVersion)' == '10.0'">c:\python34</PythonDir>
<PythonDir Condition="'$(VisualStudioVersion)' == '11.0'">c:\python34</PythonDir>
<PythonDir Condition="'$(VisualStudioVersion)' == '12.0'">c:\python34</PythonDir>
<PythonDir Condition="'$(VisualStudioVersion)' == '14.0'">c:\python36</PythonDir>
<PythonDir Condition="'$(VisualStudioVersion)' == '15.0'">c:\python36</PythonDir>
Visual Studio Property Sheets: Use Unix Line Endings This makes it easier to apply patches in the future.
2013-12-27 10:32:01 +08:00
</PropertyGroup>
<PropertyGroup>
<_PropertySheetDisplayName>glibversionpathsprops</_PropertySheetDisplayName>
</PropertyGroup>
<ItemGroup>
<BuildMacro Include="VSVer">
<Value>$(VSVer)</Value>
</BuildMacro>
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 18:37:01 +08:00
<BuildMacro Include="GlibVersion">
<Value>$(GlibVersion)</Value>
</BuildMacro>
<BuildMacro Include="ApiVersion">
<Value>$(ApiVersion)</Value>
</BuildMacro>
Visual Studio Property Sheets: Use Unix Line Endings This makes it easier to apply patches in the future.
2013-12-27 10:32:01 +08:00
<BuildMacro Include="GlibEtcInstallRoot">
<Value>$(GlibEtcInstallRoot)</Value>
</BuildMacro>
<BuildMacro Include="CopyDir">
<Value>$(CopyDir)</Value>
</BuildMacro>
<BuildMacro Include="GlibDllPrefix">
<Value>$(GlibDllPrefix)</Value>
</BuildMacro>
<BuildMacro Include="GlibDllSuffix">
<Value>$(GlibDllSuffix)</Value>
</BuildMacro>
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 17:45:44 +08:00
<BuildMacro Include="PythonDir">
<Value>$(PythonDir)</Value>
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 17:39:22 +08:00
</BuildMacro>
Visual Studio Property Sheets: Use Unix Line Endings This makes it easier to apply patches in the future.
2013-12-27 10:32:01 +08:00
</ItemGroup>
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 14:00:46 +08:00
</Project>
Reference in New Issue Copy Permalink