Blender exporter setup tips for Linux
by Mauricio T P · in Artist Corner · 02/17/2005 (7:04 am) · 1 replies
Hi. The latest exporter works great for me in both Windows and Linux, and I can confirm it works with Python 2.4 as well (Linux build). An obvious tip that generate errors is that you should make sure the version of Python in your system is the same one used to compile Blender.
As I understand it, Blender has a subset of the Python interpreter built-in during the compilation process. The DTS exporter however needs access to more classes that are not included in this minimal interpreter, that's the reason why Python needs to be installed on the system. Strange errors occur however if you have for example Python 2.4 installed on your Windows box, and is running a version of Blender compiled with Python 2.3. The built in 2.3 interpreter will try to load some 2.4 classes, and the error messages are usually cryptic.
So, in short... for Windows, just make sure the active version of Python on your system (you can configure this with the PYTHONPATH variable) is the same one embedded into your Blender binary. In the case of Blender 2.36 you need to use Python 2.3.
For Linux you have the option to recompile Blender from source if the installed version does not match the binary. In my case I am running Slackware 10.1, which comes with Python 2.4. So the Blender 2.36 Linux binary does not work out-of-the-box: download the source, reconfigure it to use Python 2.4 (this is the tricky part, the definition is in the file source/nan_definitions.mk) , and recompile.
The good news is that apparently (from my tests) the exporter code is already compliant with the changes in Python 2.4, so when Blender moves to it in the official binaries the exporter will be ready.
James, tks for the exporter, it is a great resource. If you need help in the future with the plan to convert to C++ I can probably help you, at least to get it tested and compiled in alternate platforms (Linux/OSX).
As I understand it, Blender has a subset of the Python interpreter built-in during the compilation process. The DTS exporter however needs access to more classes that are not included in this minimal interpreter, that's the reason why Python needs to be installed on the system. Strange errors occur however if you have for example Python 2.4 installed on your Windows box, and is running a version of Blender compiled with Python 2.3. The built in 2.3 interpreter will try to load some 2.4 classes, and the error messages are usually cryptic.
So, in short... for Windows, just make sure the active version of Python on your system (you can configure this with the PYTHONPATH variable) is the same one embedded into your Blender binary. In the case of Blender 2.36 you need to use Python 2.3.
For Linux you have the option to recompile Blender from source if the installed version does not match the binary. In my case I am running Slackware 10.1, which comes with Python 2.4. So the Blender 2.36 Linux binary does not work out-of-the-box: download the source, reconfigure it to use Python 2.4 (this is the tricky part, the definition is in the file source/nan_definitions.mk) , and recompile.
The good news is that apparently (from my tests) the exporter code is already compliant with the changes in Python 2.4, so when Blender moves to it in the official binaries the exporter will be ready.
James, tks for the exporter, it is a great resource. If you need help in the future with the plan to convert to C++ I can probably help you, at least to get it tested and compiled in alternate platforms (Linux/OSX).
Torque Owner Terence M.