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

107 lines
4.9 KiB
Plaintext
Raw Normal View History

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
<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<ImportGroup Label="PropertySheets">
<Import Project="glib-build-defines.props" />
</ImportGroup>
<PropertyGroup Label="UserMacros">
<BinDir>$(SolutionDir)$(Configuration)\$(Platform)\bin</BinDir>
<GlibDoInstall>
mkdir $(CopyDir)
mkdir $(CopyDir)\bin
copy $(BinDir)\$(GlibDllPrefix)glib$(GlibDllSuffix).dll $(CopyDir)\bin
copy $(BinDir)\$(GlibDllPrefix)glib$(GlibDllSuffix).pdb $(CopyDir)\bin
copy $(BinDir)\$(GlibDllPrefix)gthread$(GlibDllSuffix).dll $(CopyDir)\bin
copy $(BinDir)\$(GlibDllPrefix)gthread$(GlibDllSuffix).pdb $(CopyDir)\bin
copy $(BinDir)\$(GlibDllPrefix)gmodule$(GlibDllSuffix).dll $(CopyDir)\bin
copy $(BinDir)\$(GlibDllPrefix)gmodule$(GlibDllSuffix).pdb $(CopyDir)\bin
copy $(BinDir)\$(GlibDllPrefix)gobject$(GlibDllSuffix).dll $(CopyDir)\bin
copy $(BinDir)\$(GlibDllPrefix)gobject$(GlibDllSuffix).pdb $(CopyDir)\bin
copy $(BinDir)\$(GlibDllPrefix)gio$(GlibDllSuffix).dll $(CopyDir)\bin
copy $(BinDir)\$(GlibDllPrefix)gio$(GlibDllSuffix).pdb $(CopyDir)\bin
copy $(BinDir)\glib-genmarshal.exe $(CopyDir)\bin
copy $(BinDir)\glib-genmarshal.pdb $(CopyDir)\bin
copy $(BinDir)\gspawn-win*-helper*.exe $(CopyDir)\bin
copy $(BinDir)\gspawn-win*-helper*.pdb $(CopyDir)\bin
copy $(BinDir)\glib-compile-schemas.exe $(CopyDir)\bin
copy $(BinDir)\glib-compile-schemas.pdb $(CopyDir)\bin
copy $(BinDir)\gsettings.exe $(CopyDir)\bin
copy $(BinDir)\gsettings.pdb $(CopyDir)\bin
copy $(BinDir)\glib-compile-resources.exe $(CopyDir)\bin
copy $(BinDir)\glib-compile-resources.pdb $(CopyDir)\bin
copy $(BinDir)\gresource.exe $(CopyDir)\bin
copy $(BinDir)\gresource.pdb $(CopyDir)\bin
copy $(BinDir)\gio-querymodules.exe $(CopyDir)\bin
copy $(BinDir)\gio-querymodules.pdb $(CopyDir)\bin
copy $(BinDir)\gdbus.exe $(CopyDir)\bin
copy $(BinDir)\gdbus.pdb $(CopyDir)\bin
Visual Studio builds: Build the gio tool https://bugzilla.gnome.org/show_bug.cgi?id=768357
2016-07-04 06:43:36 +02:00
copy $(BinDir)\gio.exe $(CopyDir)\bin
copy $(BinDir)\gio.pdb $(CopyDir)\bin
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
copy ..\..\..\gio\gdbus-2.0\codegen\gdbus-codegen.in $(CopyDir)\bin\gdbus-codegen
if exist ..\..\..\gobject\glib-mkenums copy ..\..\..\gobject\glib-mkenums $(CopyDir)\bin
mkdir $(CopyDir)\include\glib-$(ApiVersion)\glib\deprecated
copy ..\..\..\msvc_recommended_pragmas.h $(CopyDir)\include\glib-$(ApiVersion)
copy ..\..\..\glib\glib.h $(CopyDir)\include\glib-$(ApiVersion)
copy ..\..\..\glib\glib-object.h $(CopyDir)\include\glib-$(ApiVersion)
#include "glib.vs10.headers"
copy ..\..\..\gmodule\gmodule.h $(CopyDir)\include\glib-$(ApiVersion)
mkdir $(CopyDir)\include\glib-$(ApiVersion)\gobject
#include "gobject.vs10.headers"
copy ..\..\..\gobject\gobjectnotifyqueue.c $(CopyDir)\include\glib-$(ApiVersion)\gobject
mkdir $(CopyDir)\include\glib-$(ApiVersion)\gio
#include "gio.vs10.headers"
mkdir $(CopyDir)\include\gio-win32-$(ApiVersion)\gio
copy ..\..\..\gio\gwin32inputstream.h $(CopyDir)\include\gio-win32-$(ApiVersion)\gio
copy ..\..\..\gio\gwin32outputstream.h $(CopyDir)\include\gio-win32-$(ApiVersion)\gio
mkdir $(CopyDir)\lib\glib-$(ApiVersion)\include
copy ..\..\..\glib\glibconfig.h $(CopyDir)\lib\glib-$(ApiVersion)\include
copy $(BinDir)\glib-$(ApiVersion).lib $(CopyDir)\lib
copy $(BinDir)\gthread-$(ApiVersion).lib $(CopyDir)\lib
copy $(BinDir)\gmodule-$(ApiVersion).lib $(CopyDir)\lib
copy $(BinDir)\gobject-$(ApiVersion).lib $(CopyDir)\lib
copy $(BinDir)\gio-$(ApiVersion).lib $(CopyDir)\lib
MSVC builds: Add scripts to generate .pc files Add a generic script, pc_base.py, which can be utilized to obtain path info, along with user-input version info, which can be used to generate pkg-config .pc files. Also enhance replace.py a bit so that it can also be used in the future to replace multiple items in a file in one shot. This is done to make building introspection files easier, as it depends much on the pkg-config .pc files to work. Update the project files so that when Python is available, we can generate the full, usable .pc files when we complete and 'install' the builds, and copy them to appropriate locations so that pkg-config can be set to find them easily.
2016-03-10 13:33:35 +01:00
mkdir $(CopyDir)\lib\pkgconfig
copy ..\gio-windows-2.0.pc $(CopyDir)\lib\pkgconfig
copy ..\gio-2.0.pc $(CopyDir)\lib\pkgconfig
copy ..\gobject-2.0.pc $(CopyDir)\lib\pkgconfig
copy ..\gmodule-no-export-2.0.pc $(CopyDir)\lib\pkgconfig
copy ..\gmodule-export-2.0.pc $(CopyDir)\lib\pkgconfig
copy ..\gmodule-2.0.pc $(CopyDir)\lib\pkgconfig
copy ..\gthread-2.0.pc $(CopyDir)\lib\pkgconfig
copy ..\glib-2.0.pc $(CopyDir)\lib\pkgconfig
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
mkdir $(CopyDir)\share\glib-$(ApiVersion)\schemas
copy ..\..\..\gio\gschema.dtd $(CopyDir)\share\glib-$(ApiVersion)\schemas
mkdir $(CopyDir)\share\glib-$(ApiVersion)\codegen
copy ..\..\..\gio\gdbus-2.0\codegen\*.py $(CopyDir)\share\glib-$(ApiVersion)\codegen
</GlibDoInstall>
MSVC builds: Add scripts to generate .pc files Add a generic script, pc_base.py, which can be utilized to obtain path info, along with user-input version info, which can be used to generate pkg-config .pc files. Also enhance replace.py a bit so that it can also be used in the future to replace multiple items in a file in one shot. This is done to make building introspection files easier, as it depends much on the pkg-config .pc files to work. Update the project files so that when Python is available, we can generate the full, usable .pc files when we complete and 'install' the builds, and copy them to appropriate locations so that pkg-config can be set to find them easily.
2016-03-10 13:33:35 +01:00
<GlibPCFiles>..\gio-windows-2.0.pc;..\gio-2.0.pc;..\gobject-2.0.pc;..\gmodule-no-export-2.0.pc;..\gmodule-export-2.0.pc;..\gmodule-2.0.pc;..\gthread-2.0.pc;..\glib-2.0.pc</GlibPCFiles>
Visual Studio builds: Refine .pc creation We may not have $(CopyDir) created, which the script that generates the .pc files check for, so create it if it is not there. This makes things a bit more convenient for people.
2016-06-15 10:21:03 +02:00
<GlibGenPC>(if not exist $(CopyDir) mkdir $(CopyDir)) &amp; (if exist $(PythonPath)\python.exe $(PythonPath)\python.exe ..\glibpc.py --prefix=$(CopyDir) --version=$(GlibVersion))</GlibGenPC>
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
</PropertyGroup>
<PropertyGroup>
<_PropertySheetDisplayName>glibinstallprops</_PropertySheetDisplayName>
</PropertyGroup>
<ItemGroup>
<BuildMacro Include="BinDir">
<Value>$(BinDir)</Value>
</BuildMacro>
<BuildMacro Include="GlibDoInstall">
<Value>$(GlibDoInstall)</Value>
</BuildMacro>
MSVC builds: Add scripts to generate .pc files Add a generic script, pc_base.py, which can be utilized to obtain path info, along with user-input version info, which can be used to generate pkg-config .pc files. Also enhance replace.py a bit so that it can also be used in the future to replace multiple items in a file in one shot. This is done to make building introspection files easier, as it depends much on the pkg-config .pc files to work. Update the project files so that when Python is available, we can generate the full, usable .pc files when we complete and 'install' the builds, and copy them to appropriate locations so that pkg-config can be set to find them easily.
2016-03-10 13:33:35 +01:00
<BuildMacro Include="GlibPCFiles">
<Value>$(GlibPCFiles)</Value>
</BuildMacro>
<BuildMacro Include="GlibGenPC">
<Value>$(GlibGenPC)</Value>
</BuildMacro>
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
</ItemGroup>
</Project>
Reference in New Issue Copy Permalink