glib/build
Chun-wei Fan 91b9aef0c9 MSVC 2010+ Projects: Update "Installation" Process
Currently, due to the way that Visual Studio 2010+ projects are handled,
the "install" project does not re-build upon changes to the sources, as it
does not believe that its dependencies have changed, although the changed
sources are automatically recompiled.  This means that if a part or more
of the solution does not build, or if the sources need some other fixes
or enhancements, the up-to-date build is not copied automatically, which
can be misleading.

Improve on the situation by forcing the "install" project to trigger its
rebuild, so that the updated binaries can be copied.  This does trigger an
MSBuild warning, but having that warning is way better than not having an
up-to-date build, especially during testing and development.
2014-06-09 10:27:36 +08:00
..
win32 MSVC 2010+ Projects: Update "Installation" Process 2014-06-09 10:27:36 +08:00
ChangeLog win32/vs8/README New files. Mention this VS solution and projects are 2009-01-13 12:13:55 +00:00
Makefile-newvs.am Support Building Using Visual Studio 2013 2014-06-03 15:50:37 +08:00
Makefile.am externals. The relevant directories and files have been svn add'ed to GLib 2008-05-17 01:36:40 +00:00
README externals. The relevant directories and files have been svn add'ed to GLib 2008-05-17 01:36:40 +00:00

Now this directory is private to GLib. Only the files relevant to GLib
are left. See the separate "build" module in GNOME SVN for history.