Commit Graph

11 Commits

Author SHA1 Message Date
Chun-wei Fan
3c4ee831f7 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
Chun-wei Fan
97b82d8d21 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
Chun-wei Fan
d858cd3047 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
Chun-wei Fan
d8de88e541 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
Tor Lillqvist
226cc663e4 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:15:02 +02:00
Tor Lillqvist
79eb03aa4f Use README.txt instead of README for Windows developer friendliness 2010-02-04 14:54:28 +02:00
Tor Lillqvist
9d444f7b12 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:53:44 +02:00
Tor Lillqvist
57d3e4cba3 Include also testglib.vcproj in tarball 2010-02-02 21:26:01 +02:00
Tor Lillqvist
0f35c33ecf 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
Tor Lillqvist
9d3d04412b 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
Tor Lillqvist
47d23c1888 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