Updated the docs for building blender using cygwin/gcc.

Thanks for the input Pjotr!

1 files changed, 17 insertions, 8 deletions

diff --git a/doc/README.windows-gcc b/doc/README.windows-gcc
index e20e7ff5585..c8f94ba4297 100644
--- a/doc/README.windows-gcc
+++ b/doc/README.windows-gcc
@@ -1,5 +1,5 @@
 Here are some basic instructions for building
-blender blender for windows using gcc under cygwin.
+blender for windows using gcc under cygwin.
 Please note that the resulting executable does not
 depend on cygwin and can be distrubuted to machines
 that don't have cygwin installed.
@@ -8,9 +8,9 @@ The instructions are:
 
 1. Download cygwin (www.cygwin.com) and use the setup program
    to install packages for gcc, gcc-mingw, w32api, make, cvs,
-   python, and perl (and maybe others... the dependency list
-   is bound to change over time and hopefully these instructions
-   will keep with the changes). All of the following
+   python, perl, gettext, and gettext-devel (and maybe others... the 
+   dependency list is bound to change over time and hopefully these 
+   instructions will keep up with the changes). All of the following
    commands will be entered at the cygwin prompt so launch
    cygwin now.
 
@@ -19,20 +19,20 @@ The instructions are:
      mkdir bf-blender
      cd bf-blender
 
-3. checkout the blender module from the bf-blender tree using cvs 
+3. Checkout the blender module from the bf-blender tree using cvs 
    (use password anonymous):
      cvs -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender login
      cvs -z3 -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender \
           co blender
 
-4. checkout the lib/windows module from bf-blender using cvs:
+4. Checkout the lib/windows module from bf-blender using cvs:
      cvs -z3 -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender \
           co lib/windows
 
 5. Enter the newly created blender directory:
      cd blender
 
-6. to prepare the build system to use only the free tools we must
+6. To prepare the build system to use only the free tools we must
    set some environment variables. This is done by creating a
    file called "user-def.mk" in the blender directory and
    inserting the following line with notepad or your favorite
@@ -73,6 +73,9 @@ Some final notes
   based laptop).
 - If the build is successful you will find it has created
   the program obj/windows/bin/blender.exe
+- The executable generated by gcc will generally be slower
+  that an msvc++ generated executable at rendering, but the 
+  OpenGL speed should be about the same.
 - Sound is disabled
 - If you want to clean your sources issue a 'make clean'
   in the top blender directory.
@@ -88,4 +91,10 @@ Some final notes
   to your buddies? Try "make release" ... read the output
   to find out where the zip file was placed (note: you will
   probably need the zip/unzip packages from cygwin to do
-  this)
+  this).
+- You can make a debug executable using 'make debug'. The
+  debug executable will be larger and slower that the
+  regular executable, but when used with the gnu debugger
+  (gdb) it can help debug a blender problem (for example,
+  it can locate the line of code that caused blender to
+  crash).