I'm using 'visual-3.0-20040722.tar.gz'.
The config.log and the resulting top-level Makefile claim the visual
version is 2.9.7, I think because the 'configure' script has these
lines:
PACKAGE_VERSION='2.9.7'
PACKAGE_STRING='Visual Python 2.9.7'
Should the version become 3.0.0?
A few updates for the 'INSTALL.txt':
I'm using Debian testing (sarge). To build visual-3.0 I had to
install xlibmesa-gl-dev and xlibmesa-glu-dev to get 'GL/gl.h' and
'GL/glu.h' (needed when compiling 'cylinder.cpp'). These are the
error lines I saw before I installed those packages:
xgl.h:22:19: GL/gl.h: No such file or directory
xgl.h:23:20: GL/glu.h: No such file or directory
Sarge now (4 Dec 2004) has v1.31 of libboost-python-dev so no need to
use python2.2 packages or to forage in Sid.
So the one-shot apt-get line I recommend is:
apt-get install python2.3-{dev,numeric} g++-3.3 {libboost-python,xlibmesa-gl{,u},gtkglarea5,libgtk1.2}-dev
or with \ to break the long line:
apt-get install python2.3-{dev,numeric} g++-3.3 \
{libboost-python,xlibmesa-gl{,u},gtkglarea5,libgtk1.2}-dev
Either is equivalent to:
apt-get install python2.3-dev python2.3-numeric g++-3.3 \
libboost-python-dev xlibmesa-gl-dev xlibmesa-glu-dev \
gtkglarea5-dev libgtk1.2-dev
I couldn't compile visual on my 96MB Pentium (586) laptop -- the g++
compile of 'cvisualmodule.cpp' consumed over 150MB of virtual memory
(c++ is an absurd language)! The cc1plus process got about 2% of the
CPU time while swapping like mad. I then compiled everything on a
nearby workstation with more memory, but is there any way to reduce
the memory consumption?
-Sanjoy
|
