summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChun-wei Fan <fanchunwei@src.gnome.org>2011-07-25 11:53:27 +0800
committerChun-wei Fan <fanchunwei@src.gnome.org>2011-07-25 11:53:27 +0800
commit7ac3b46beaa57703aa46e85d7300b3d5184eb028 (patch)
tree0ae6d970279e834fe946a9cb5eff4ab93b0cf5a0
parent2574242575e6a1d7184bb43c61ba3090de611971 (diff)
downloadpango-7ac3b46beaa57703aa46e85d7300b3d5184eb028.tar.gz
Update VS 2008 README.txt
Tell people not to compile Pango in paths with spaces in them.
-rw-r--r--build/win32/vs9/README.txt5
1 files changed, 4 insertions, 1 deletions
diff --git a/build/win32/vs9/README.txt b/build/win32/vs9/README.txt
index a053efbb..d4ef37e0 100644
--- a/build/win32/vs9/README.txt
+++ b/build/win32/vs9/README.txt
@@ -1,12 +1,15 @@
Note that all this is rather experimental.
+Please do not compile Pango in a path with spaces to avoid potential
+problems during the build and/or during the usage of the Pango
+library.
+
This VS9 solution and the projects it includes are intented to be used
in a Pango source tree unpacked from a tarball. In a git checkout you
first need to use some Unix-like environment or manual work to expand
files as needed, for instance the .vcprojin files here into .vcproj
files.
-
It is recommended that GLib is compiled with VS9 to compile Pango.
External dependencies are at least Cairo, zlib, libpng,
gettext-runtime; optional dependencies include fontconfig, freetype,