Further work on VS9 project files

[platform/upstream/glib.git] / build / win32 / vs9 / README.txt

diff --git a/build/win32/vs9/README.txt b/build/win32/vs9/README.txt
index 86620ec..662cb2a 100644 (file)
--- 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 <root>:\r
 \r
 <root>\glib\<this-glib-source-tree>\r
-<root>\glib\dependencies\<PlatformName>\proxy-libintl\r
+<root>\vs9\<PlatformName>\r
 \r
 *this* file you are now reading is thus located at\r
 <root>\glib\<this-glib-source-tree>\build\win32\vs9\README.\r
 \r
 <PlatformName> is either Win32 or x64, as in VS9 project files.\r
 \r
-<root>\glib\dependencies\<PlatformName>\proxy-libintl contains the\r
-unpacked proxy-libintl zip file, so that for instance libintl.h is at\r
-<root>\glib\dependencies\<PlatformName>\proxy-libintl\include\libintl.h.\r
+You should unpack the proxy-libintl-dev zip file into\r
+<root>\vs9\<PlatformName>, so that for instance libintl.h end up at\r
+<root>\vs9\<PlatformName>\include\libintl.h.\r
+\r
+The "install" project will copy build results and headers into their\r
+appropriate location under <root>\vs9\<PlatformName>. For instance,\r
+built DLLs go into <root>\vs9\<PlatformName>\bin, built LIBs into\r
+<root>\vs9\<PlatformName>\lib and GLib headers into\r
+<root>\vs9\<PlatformName>\include\glib-2.0. This is then from where\r
+project files higher in the stack are supposed to look for them, not\r
+from a specific GLib source tree.\r
 \r
 --Tor Lillqvist <tml@iki.fi>\r