luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-11-14 05:16:18 +01:00
Code Issues Packages Projects Releases Wiki Activity
0d69e553fd
glib/win32/vs10/gmodule.vcxproj.filters

31 lines
1.2 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 ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<ItemGroup>
<Filter Include="Source Files">
<UniqueIdentifier>{4FC737F1-C7A5-4376-A066-2A32D752A2FF}</UniqueIdentifier>
<Extensions>cpp;c;cc;cxx;def;odl;idl;hpj;bat;asm;asmx</Extensions>
</Filter>
<Filter Include="Header Files">
<UniqueIdentifier>{93995380-89BD-4b04-88EB-625FBE52EBFB}</UniqueIdentifier>
<Extensions>h;hpp;hxx;hm;inl;inc;xsd</Extensions>
</Filter>
<Filter Include="Resource Files">
<UniqueIdentifier>{67DA6AB6-F800-4c08-8B7A-83BB121AAD01}</UniqueIdentifier>
<Extensions>rc;ico;cur;bmp;dlg;rc2;rct;bin;rgs;gif;jpg;jpeg;jpe;resx;tiff;tif;png;wav</Extensions>
</Filter>
</ItemGroup>
<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 07:00:46 +01:00
<ClCompile Include="..\..\gmodule\gmodule.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
<Filter>Source Files</Filter>
</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>
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
<CustomBuild Include="..\..\gmodule\gmoduleconf.h.win32"><Filter>Resource Files</Filter></CustomBuild>
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>
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>
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
<ResourceCompile Include="..\..\gmodule\gmodule.rc">
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
<Filter>Resource Files</Filter>
</ResourceCompile>
</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 07:00:46 +01:00
</Project>
Reference in New Issue Copy Permalink