From 3d3b101541c51a1962c494927fcc013bce6188fe Mon Sep 17 00:00:00 2001
From: Ton Roosendaal
-
This is what you should get from a downloaded Blender package:
@@ -61,6 +60,55 @@ plugins and more. coders and the CVS repository with the sources can be found at the developer's site. +Installing is mostly a matter of executing a self-installer package or unpacking it to +some folder. Blender has a minimum of system dependencies (like OpenGL and SDL), and doesn't +install by overwriting libraries in your system. There are also some extra +files needed for a good install, like an antialiased font and standard python scripts, but these +are optional. Typically these will go to your HOME/.blender/ +directory. Below you find instructions for it per OS. +
+ +Windows: the .exe installer handles registry of file types for you. The .zip download has
+a .blender directory included, which can be manually copied.
+The directory .blender is located by Blender while checking the following list:
+- whether environment variable HOME exists,
+- or, if environment USERPROFILE exists, and the installer has created there the Application Data\Blender Foundation\Blender\
+directory,
+- or it uses the .blender directory from the installation directory (where blender.exe resides)
+Also note that Blender comes with two dll files, which have to reside next to blender.exe.
Linux, FreeBSD, Irix, Solaris: after unpacking the distribution, you can copy the .blender +directory from it to your home directory.
+ +OSX: the .blender directory is in Blender.app/Contents/Resources/. This is being located +by default. If you like to alter some of the files, copy this directory to your home dir.
+ +Other settings:
+There are many paths you can set in Blender itself, to tell it where to
+look for your collections of texture and sound files, fonts, plugins and
+additional scripts, besides where it should save rendered images, temporary
+data, etc. If you're only starting, there's no need to worry about this now.
+
Python:
+Some downloaded scripts may require extra Python modules not shipped with
+Blender. Installing the whole Python distribution is a way to solve this
+issue for most cases except scripts that require extensions (3rd party
+modules), but we are starting to add more modules to Blender itself so that
+most scripts don't depend on full Python installs anymore.
Even if you do have the right version of Python installed you may need to +tell the embedded Python interpreter where the installation is. To do that +it's enough to set a system variable called PYTHON to the full path to the +stand-alone Python executable (to find out execute "import sys; print +sys.executable" inside the stand-alone interpreter, not in Blender). To check +which Python was linked to your Blender binary, execute "import sys; print +sys.version" at Blender's text editor), it's probably 2.3.something -- only the +two first numbers should have to match with yours.
+ +If you are reading this, you probably already have Blender installed. -Anyway, it's a matter of executing a self-installer package or unpacking it to -some folder.
- -There are many paths you can set in Blender itself, to tell it where to -look for your collections of texture and sound files, fonts, plugins and -additional scripts, besides where it should save rendered images, temporary -data, etc. If you're only starting, there's no need to worry about this now. -
- -Some downloaded scripts may require extra Python modules not shipped with -Blender. Installing the whole Python distribution is a way to solve this -issue for most cases except scripts that require extensions (3rd party -modules), but we are starting to add more modules to Blender itself so that -most scripts don't depend on full Python installs anymore.
- -Even if you do have the right version of Python installed you may need to -tell the embedded Python interpreter where the installation is. To do that -it's enough to set a system variable called PYTHON to the full path to the -stand-alone Python executable (to find out execute "import sys; print -sys.executable" inside the stand-alone interpreter, not in Blender). To check -which Python was linked to your Blender binary, execute "import sys; print -sys.version" at Blender's text editor), it's probably 2.3.something -- only the -two first numbers should have to match with yours.
-Depending on your platform, the installation may have put an icon on your -- cgit v1.2.3