glib/build/win32
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
..
dirent Bug 545954 - 64-bit issue in dirent 2008-08-02 08:43:30 +00:00
vs8 win32/vs8/README New files. Mention this VS solution and projects are 2009-01-13 12:13:55 +00:00
vs9 Fix GLib MSVC Project 2014-01-06 12:31:18 +08:00
vs10 MSVC 2010+ Projects: Update "Installation" Process 2014-06-09 10:27:36 +08:00
vs11 Support Building Using Visual Studio 2013 2014-06-03 15:50:37 +08:00
vs12 Support Building Using Visual Studio 2013 2014-06-03 15:50:37 +08:00
make.msc Simplified for pre-built package use 2009-05-30 15:08:29 +02:00
Makefile.am Support Building Using Visual Studio 2013 2014-06-03 15:50:37 +08:00
module.defs Simplified for pre-built package use 2009-05-30 15:08:29 +02:00
setup.py add a script to generator files for building 2011-07-06 08:04:08 +08:00