luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-02-06 11:00:57 +01:00
Code Issues Packages Projects Releases Wiki Activity
glib/build/win32/vs9/Makefile.am

26 lines
548 B
Makefile
Raw Normal View History

New folder. Project files for use with MSVS9. Based on the MSVS8 project 2008-09-16 Tor Lillqvist <tml@novell.com> * win32/vs9: New folder. Project files for use with MSVS9. Based on the MSVS8 project files is win32/vs8. Four configurations: Debug|Win32, Release|Win32, Debug|x64 and Release|x64. DLL names simplified to of the style glib-2-vs9.dll. svn path=/trunk/; revision=7497
2008-09-15 22:59:44 +00:00
EXTRA_DIST = \
Use README.txt instead of README for Windows developer friendliness
2010-02-04 14:51:56 +02:00
README.txt \
New folder. Project files for use with MSVS9. Based on the MSVS8 project 2008-09-16 Tor Lillqvist <tml@novell.com> * win32/vs9: New folder. Project files for use with MSVS9. Based on the MSVS8 project files is win32/vs8. Four configurations: Debug|Win32, Release|Win32, Debug|x64 and Release|x64. DLL names simplified to of the style glib-2-vs9.dll. svn path=/trunk/; revision=7497
2008-09-15 22:59:44 +00:00
glib.sln \
glib.vcproj \
Avoid much of duplication in lists of source files Don't keep the lists of source files for libglib, libgobject and libgio in the VS project files in addition to the canonical location, the corresponding Makefile.am files. Instead, generate the corresponding .vcproj files at make dist time using the C preprocessor, from template files called .vcprojin. We still list explicitly in the .vcprojin files some of the Windows-specific source files, and the sources files of gnulib and pcre.
2010-03-21 16:11:49 +02:00
glib.vcprojin \
Refactor VS9 project files Factor out common parts into a vsprops file. Drop empty elements for tools that aren't used.
2010-02-04 14:36:23 +02:00
glib-genmarshal.vcproj \
win32/vs8/README New files. Mention this VS solution and projects are 2009-01-13 Tor Lillqvist <tml@novell.com> * win32/vs8/README * win32/vs9/README: New files. Mention this VS solution and projects are experimental and that https://code.launchpad.net/oah might be a better choice. * win32/vs8/Makefile.am * win32/vs9/Makefile.am (EXTRA_DIST): Add the READMEs and two missing vcproj files. svn path=/trunk/; revision=7806
2009-01-13 12:13:55 +00:00
gspawn-win32-helper-console.vcproj \
gspawn-win32-helper.vcproj \
Refactor VS9 project files Factor out common parts into a vsprops file. Drop empty elements for tools that aren't used.
2010-02-04 14:36:23 +02:00
gmodule.vcproj \
gobject.vcproj \
Avoid much of duplication in lists of source files Don't keep the lists of source files for libglib, libgobject and libgio in the VS project files in addition to the canonical location, the corresponding Makefile.am files. Instead, generate the corresponding .vcproj files at make dist time using the C preprocessor, from template files called .vcprojin. We still list explicitly in the .vcprojin files some of the Windows-specific source files, and the sources files of gnulib and pcre.
2010-03-21 16:11:49 +02:00
gobject.vcprojin \
Add an "install" project that copies the deliverables into a place from which projects in other packages will use them. svn path=/trunk/; revision=7499
2008-09-16 01:04:55 +00:00
gthread.vcproj \
Refactor VS9 project files Factor out common parts into a vsprops file. Drop empty elements for tools that aren't used.
2010-02-04 14:36:23 +02:00
gio.vcproj \
Avoid much of duplication in lists of source files Don't keep the lists of source files for libglib, libgobject and libgio in the VS project files in addition to the canonical location, the corresponding Makefile.am files. Instead, generate the corresponding .vcproj files at make dist time using the C preprocessor, from template files called .vcprojin. We still list explicitly in the .vcprojin files some of the Windows-specific source files, and the sources files of gnulib and pcre.
2010-03-21 16:11:49 +02:00
gio.vcprojin \
Add VS 2008 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 13:47:07 +08:00
glib-compile-schemas.vcproj \
gsettings.vcproj \
Add Visual C++ 2008 projects for GResource tools Add projects to build the glib-compile-resources and gresource(-tool) utilities, and "install" these tools upon successful compilation, and dist the new projects. One piece of note: will it be better to dist gconstructor_as_data.h instead of generating it in the VS build process (I generated it in the property sheet update in this commit)? Visual C++ 2010 projects will follow shortly.
2012-02-07 14:37:57 +08:00
glib-compile-resources.vcproj \
gresource.vcproj \
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 15:48:32 +08:00
gio-querymodules.vcproj \
gdbus.vcproj \
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 12:49:42 +08:00
glib-install.vcproj \
MSVC 2008 Projects: Split the Property Sheets Split the property sheet into four sheets, to make maintainance of the build files easier, and also to prepare for using autotools to fill in the parts for the "installation" of headers. Also put more of the items that are repeated in the projects into the property sheets, also to improve ease of maintenance. Updates to the Visual Studio 2010 projects will come later, as the script to update them to Visual Studio 2012 must also be taken into account during' the process.
2013-08-21 16:05:47 +08:00
glib-build-defines.vsprops \
glib-install.vsprops \
glib-version-paths.vsprops \
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 12:25:18 +08:00
glib-gen-srcs.vsprops
Reference in New Issue Copy Permalink