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

[Carl Worth]

 src/end_to_end_build_for_win32.mdwn |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

New commits:
commit adb772372435ec4140cc476dd0357a315ce25402
Author: travisgriggs <travisgriggs at web>
Date:   Mon Nov 2 23:10:05 2009 -0800

diff --git a/src/end_to_end_build_for_win32.mdwn b/src/end_to_end_build_for_win32.mdwn
index 4acff36..163ad06 100644
--- a/src/end_to_end_build_for_win32.mdwn
+++ b/src/end_to_end_build_for_win32.mdwn
@@ -96,12 +96,12 @@ This will produce a bunch of scary looking warning text. Some of it yellow. It's
 
 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.
 
-       sed s/RuntimeLibrary=.2./RuntimeLibrary=0/ zlib.vcproj > fixed.vcproj
+       sed /RuntimeLibrary=/s/2/0/ zlib.vcproj > fixed.vcproj
        move /Y fixed.vcproj zlib.vcproj
-       <i>...or open zlib.vcproj with Wordpad and use a search/replace to change all RuntimeLibrary="2" to RuntimeLibrary="0"</i>
+<i>...or open zlib.vcproj with Wordpad and use a search/replace to change all RuntimeLibrary="2" to RuntimeLibrary="0"</i>
 
 
-Finally build it
+Finally, build it
 
        vcbuild zlib.vcproj "LIB Release"