[cairo-commit] [cairo-www] src/end_to_end_build_for_win32.mdwn

[Carl Worth]

 src/end_to_end_build_for_win32.mdwn |    2 ++
 1 file changed, 2 insertions(+)

New commits:
commit e3d47f661dff1a66abcad3e9907909fd5681b04f
Author: travisgriggs <travisgriggs at web>
Date:   Mon Nov 2 15:35:04 2009 -0800

diff --git a/src/end_to_end_build_for_win32.mdwn b/src/end_to_end_build_for_win32.mdwn
index a4c81a1..f184c51 100644
--- a/src/end_to_end_build_for_win32.mdwn
+++ b/src/end_to_end_build_for_win32.mdwn
@@ -89,6 +89,8 @@ Now we can upgrade it. This does whatever needs to happen so we can build it wit
 
        vcbuild /upgrade zlib.vcproj
 
+This will produce a bunch of scary looking warning text. Some of it yellow. It's ok, ignore it.
+
 Our next problem is, that the project file, by default is configured to build with the /MD option, which means it will be dynamically linked to the Microsoft runtime. This will be a problem if it links to the current MS runtime library, because target deployment machines won't necessarily have that specific version. There is no real dependency on a particular version. So it's easier to compile that statically in. It doesn't make the library that much bigger.
 
 "Now patch the proj file to build MT (static) instead of MD (dynamic)"