Updated the docs for building blender using cygwin/gcc.

Thanks for the input Pjotr!
This commit is contained in:
Chris Want
2003-05-30 15:50:09 +00:00
parent 3c7c20676e
commit fb76c8ac76

View File

@@ -1,5 +1,5 @@
Here are some basic instructions for building 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 Please note that the resulting executable does not
depend on cygwin and can be distrubuted to machines depend on cygwin and can be distrubuted to machines
that don't have cygwin installed. that don't have cygwin installed.
@@ -8,9 +8,9 @@ The instructions are:
1. Download cygwin (www.cygwin.com) and use the setup program 1. Download cygwin (www.cygwin.com) and use the setup program
to install packages for gcc, gcc-mingw, w32api, make, cvs, to install packages for gcc, gcc-mingw, w32api, make, cvs,
python, and perl (and maybe others... the dependency list python, perl, gettext, and gettext-devel (and maybe others... the
is bound to change over time and hopefully these instructions dependency list is bound to change over time and hopefully these
will keep with the changes). All of the following instructions will keep up with the changes). All of the following
commands will be entered at the cygwin prompt so launch commands will be entered at the cygwin prompt so launch
cygwin now. cygwin now.
@@ -19,20 +19,20 @@ The instructions are:
mkdir bf-blender mkdir bf-blender
cd 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): (use password anonymous):
cvs -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender login cvs -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender login
cvs -z3 -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender \ cvs -z3 -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender \
co 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 \ cvs -z3 -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender \
co lib/windows co lib/windows
5. Enter the newly created blender directory: 5. Enter the newly created blender directory:
cd blender 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 set some environment variables. This is done by creating a
file called "user-def.mk" in the blender directory and file called "user-def.mk" in the blender directory and
inserting the following line with notepad or your favorite inserting the following line with notepad or your favorite
@@ -73,6 +73,9 @@ Some final notes
based laptop). based laptop).
- If the build is successful you will find it has created - If the build is successful you will find it has created
the program obj/windows/bin/blender.exe 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 - Sound is disabled
- If you want to clean your sources issue a 'make clean' - If you want to clean your sources issue a 'make clean'
in the top blender directory. in the top blender directory.
@@ -88,4 +91,10 @@ Some final notes
to your buddies? Try "make release" ... read the output to your buddies? Try "make release" ... read the output
to find out where the zip file was placed (note: you will to find out where the zip file was placed (note: you will
probably need the zip/unzip packages from cygwin to do 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).