luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-11-11 20:06:18 +01:00
Code Issues Packages Projects Releases Wiki Activity
700983c8c9
glib/build/win32/vs10/Makefile.am

43 lines
1.1 KiB
Makefile
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
EXTRA_DIST = \
README.txt \
glib.sln \
glib.vcxproj \
glib.vcxproj.filters \
glib.vcxprojin \
glib.vcxproj.filtersin \
glib-genmarshal.vcxproj \
glib-genmarshal.vcxproj.filters \
gspawn-win32-helper-console.vcxproj \
gspawn-win32-helper-console.vcxproj.filters \
gspawn-win32-helper.vcxproj \
gspawn-win32-helper.vcxproj.filters \
gmodule.vcxproj \
gmodule.vcxproj.filters \
gobject.vcxproj \
gobject.vcxproj.filters \
gobject.vcxprojin \
gobject.vcxproj.filtersin \
gthread.vcxproj \
gthread.vcxproj.filters \
gio.vcxproj \
gio.vcxproj.filters \
gio.vcxprojin \
gio.vcxproj.filtersin \
Add VS 2010 compilation support for some utilities -Added projects to compile the glib-compile-schemas and gsettings utilities -Update .vsprops to install these in "install" phase -Distribute these projects also
2011-04-25 07:32:18 +02:00
glib-compile-schemas.vcxproj \
glib-compile-schemas.vcxproj.filters \
gsettings.vcxproj \
gsettings.vcxproj.filters \
Add Visual C++ 2010 projects to compile GResource tools Added projects to compile the glib-compile-resources and gresource(-tool) utility programs during the Visual C++ 2010 build process, "install" the resulting binaries upon successful compilation, and dist the new .vcxproj and .vcxproj.filters files. Also updated the property sheet and "install" project to make sure the new .exe's are indeed "installed" and removed from the "install" project the dependency on the testglib project as testglib is not an exhausive test on GLib and people might want to make that project compile different test programs as they might need. Just wondering: I have updated the property sheet to create the gconstructor_as_data.h header for glib-compile-resources, but is it better to dist that generated header instead as the VS 2008/2010 projects will depend on a working installation of PERL on Windows?
2012-02-07 10:05:22 +01:00
glib-compile-resources.vcxproj \
glib-compile-resources.vcxproj.filters \
gresource.vcxproj \
gresource.vcxproj.filters \
Add MSVC Projects for Utility Programs Build and "install" the gio-querymodules and gdbus utility programs so that the Visual Studio builds of GLib is more comprehensive. The Python scripts for the GDBus codegen will be added to "installation" later.
2013-06-20 09:48:32 +02:00
gio-querymodules.vcxproj \
gio-querymodules.vcxproj.filters \
gdbus.vcxproj \
gdbus.vcxproj.filters \
MSVC Builds: Rename "install" Projects Rename the project to "install" the GLib files, as we are planning to have a grand solution file that would build the entire GTK+ stack with its deps, to ease the process for people building the GTK+ stack from a stock installation of Visual Studio.
2015-02-02 05:49:42 +01:00
glib-install.vcxproj \
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
glib-build-defines.props \
glib-install.props \
glib-version-paths.props \
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
glib-gen-srcs.props
Reference in New Issue Copy Permalink