diff options
author | Behdad Esfahbod <behdad@behdad.org> | 2010-03-30 15:07:35 -0400 |
---|---|---|
committer | Behdad Esfahbod <behdad@behdad.org> | 2010-03-30 15:11:37 -0400 |
commit | d98a35b04f57cebdfdbe40750cd1fa998c730c42 (patch) | |
tree | 0c364238aa9be2a25dbc7e16d1a41f8a968b6bac /build/win32/vs9/README.txt | |
parent | d2be51b19cc4ff2f49ee56ca42782f1c1e57fe2c (diff) | |
download | pango-d98a35b04f57cebdfdbe40750cd1fa998c730c42.tar.gz |
Revert "Remove the .vcproj files before rewriting them"
Revert .vcproj files and accompanying commits as the build stuff
needs more work.
Diffstat (limited to 'build/win32/vs9/README.txt')
-rw-r--r-- | build/win32/vs9/README.txt | 35 |
1 files changed, 0 insertions, 35 deletions
diff --git a/build/win32/vs9/README.txt b/build/win32/vs9/README.txt deleted file mode 100644 index b7c4e908..00000000 --- a/build/win32/vs9/README.txt +++ /dev/null @@ -1,35 +0,0 @@ -Note that all this is rather experimental.
-
-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.
-
-Set up the source tree as follows under some arbitrary top folder
-<root>:
-
-<root>\pango\<this-pango-source-tree>
-<root>\vs9\<PlatformName>
-
-*this* file you are now reading is thus located at
-<root>\pango\<this-pango-source-tree>\build\win32\vs9\README.txt.
-
-<PlatformName> is either Win32 or x64, as in VS9 project files.
-
-You should unpack the glib-dev zip file into
-<root>\vs9\<PlatformName>, so that for instance glib.h ends up at
-<root>\vs9\<PlatformName>\include\glib-2.0\glib.h.
-
-The "install" project will copy build results and headers into their
-appropriate location under <root>\vs9\<PlatformName>. For instance,
-built DLLs go into <root>\vs9\<PlatformName>\bin, built LIBs into
-<root>\vs9\<PlatformName>\lib and headers into
-<root>\vs9\<PlatformName>\include\pangpo-1.0. This is then from where
-project files higher in the stack are supposed to look for them, not
-from a specific Pango source tree like this one. It is important to
-keep separate the concept of a "source tree", where also non-public
-headers are present, and an "install tree" where only public headers
-are present.
-
---Tor Lillqvist <tml@iki.fi>
|