From 762e18d8cebf907e51aed14298525048f7c9e015 Mon Sep 17 00:00:00 2001 From: Tor Lillqvist Date: Thu, 4 Feb 2010 19:57:38 +0200 Subject: [PATCH] Further work on VS9 project files --- build/win32/vs9/README.txt | 16 ++++++++++++---- build/win32/vs9/glib.vsprops | 32 ++++++++++++++++++++++++++++++-- build/win32/vs9/install.vcproj | 8 ++++---- 3 files changed, 46 insertions(+), 10 deletions(-) diff --git a/build/win32/vs9/README.txt b/build/win32/vs9/README.txt index 86620ec1a..662cb2a9e 100644 --- a/build/win32/vs9/README.txt +++ b/build/win32/vs9/README.txt @@ -15,15 +15,23 @@ builds. Set up the source tree as follows under some arbitrary top folder : \glib\ -\glib\dependencies\\proxy-libintl +\vs9\ *this* file you are now reading is thus located at \glib\\build\win32\vs9\README. is either Win32 or x64, as in VS9 project files. -\glib\dependencies\\proxy-libintl contains the -unpacked proxy-libintl zip file, so that for instance libintl.h is at -\glib\dependencies\\proxy-libintl\include\libintl.h. +You should unpack the proxy-libintl-dev zip file into +\vs9\, so that for instance libintl.h end up at +\vs9\\include\libintl.h. + +The "install" project will copy build results and headers into their +appropriate location under \vs9\. For instance, +built DLLs go into \vs9\\bin, built LIBs into +\vs9\\lib and GLib headers into +\vs9\\include\glib-2.0. This is then from where +project files higher in the stack are supposed to look for them, not +from a specific GLib source tree. --Tor Lillqvist diff --git a/build/win32/vs9/glib.vsprops b/build/win32/vs9/glib.vsprops index 75006d495..5a9c092e8 100644 --- a/build/win32/vs9/glib.vsprops +++ b/build/win32/vs9/glib.vsprops @@ -8,14 +8,14 @@ > + diff --git a/build/win32/vs9/install.vcproj b/build/win32/vs9/install.vcproj index 94c28dc97..6f30f58fa 100644 --- a/build/win32/vs9/install.vcproj +++ b/build/win32/vs9/install.vcproj @@ -22,7 +22,7 @@