X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=build%2Fwin32%2Fvs9%2FREADME.txt;h=662cb2a9ebbeb4def886587d45c76d55ca11b3f8;hb=762e18d8cebf907e51aed14298525048f7c9e015;hp=86620ec1a38e466ee51da6ebcb2c6ac096e71758;hpb=021643cda4f9b13fd72e898165744e9aefb346cd;p=platform%2Fupstream%2Fglib.git diff --git a/build/win32/vs9/README.txt b/build/win32/vs9/README.txt index 86620ec..662cb2a 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