92 lines
3.4 KiB
Plaintext
92 lines
3.4 KiB
Plaintext
|
Here are some basic instructions for building
|
||
|
blender 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.
|
||
|
|
||
|
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
|
||
|
commands will be entered at the cygwin prompt so launch
|
||
|
cygwin now.
|
||
|
|
||
|
2. Create a directory to put your sources and then enter that
|
||
|
directory, e.g.:
|
||
|
mkdir bf-blender
|
||
|
cd bf-blender
|
||
|
|
||
|
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:
|
||
|
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
|
||
|
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
|
||
|
text editor:
|
||
|
export FREE_WINDOWS=true
|
||
|
|
||
|
The quickest way to do this though is to issue the following
|
||
|
command:
|
||
|
echo 'export FREE_WINDOWS=true' > user-def.mk
|
||
|
|
||
|
7. Time to build... issue the command:
|
||
|
make
|
||
|
|
||
|
8. Wait for it to finish (there is this mysterious place called
|
||
|
'outside' that I am told is nice to go to while waiting for a
|
||
|
compile to finish).
|
||
|
|
||
|
Getting Help
|
||
|
------------
|
||
|
If you have problems, come by #blendersauce on irc.freenode.net
|
||
|
or post questions to the "Compiling, Libraries, Modules" forum
|
||
|
at www.blender.org. There is also the very useful bf-committers
|
||
|
mailing list, what you can subscribe to here:
|
||
|
|
||
|
http://www.blender.org/mailman/listinfo/bf-committers
|
||
|
(as a bonus you can get info about the most recent features that
|
||
|
are coming down the pipe ...)
|
||
|
|
||
|
This said, the most common fix to a problem will
|
||
|
probably involve installing an additional cygwin package,
|
||
|
so keep that cygwin setup program close by ...
|
||
|
|
||
|
Some final notes
|
||
|
----------------
|
||
|
|
||
|
- The build will take a long time, even on a fast machine
|
||
|
(a clean build takes almost an hour on my Athlon 1800+
|
||
|
based laptop).
|
||
|
- If the build is successful you will find it has created
|
||
|
the program obj/windows/bin/blender.exe
|
||
|
- Sound is disabled
|
||
|
- If you want to clean your sources issue a 'make clean'
|
||
|
in the top blender directory.
|
||
|
- If you want to update your sources when somebody has
|
||
|
added a new awesome feature, you will want to go to the
|
||
|
topmost blender directory and issue the following command:
|
||
|
cvs -z3 update -P -d
|
||
|
It would probably be best to clean your sources before
|
||
|
re-building (see previous note).
|
||
|
- This is a work in progress, so some things may not be working
|
||
|
right or it may not support all of the cutting edge features.
|
||
|
- Want to make a fancy zipped up blender package to give
|
||
|
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)
|