Chun-wei Fan 8e88a2e136 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 11:48:54 +08:00
..
win32	MSVC 2010+ Projects: Update "Installation" Process	2014-06-09 11:48:54 +08:00
detectenv_msvc.mak	build/: Rename a Shared MSVC NMake Makefile	2014-01-13 17:19:07 +08:00
gen-file-list-gtk.py	Visual C++ Builds: Build Introspection for GdkWin32	2014-04-03 15:49:05 +08:00
gtk-introspection-msvc.mak	Visual C++ Builds: Build Introspection for GdkWin32	2014-04-03 15:49:05 +08:00
introspection-msvc.mak	MSVC Builds: Rework Introspection Build	2014-01-13 16:05:32 +08:00
Makefile.am	build/: Rename a Shared MSVC NMake Makefile	2014-01-13 17:19:07 +08:00
msvcfiles.py	MSVC Builds: Rework Introspection Build	2014-01-13 16:05:32 +08:00