From: Andy D. <dou...@la...> - 2004-06-14 16:17:46
|
On Fri, 11 Jun 2004, Jonathan Brandmeyer wrote: > VPython 2.9.4 is ready for download from > http://sourceforge.net/project/showfiles.php?group_id=6013 I had a few configure nits with this version. Specifically, I built it with the following options: (the use of python 2.2 is because my Debian testing system only has boost 1.30) #!/bin/sh PYTHON=/usr/bin/python2.2 export PYTHON PYTHONPATH=/opt/python/lib/python2.2/site-packages export PYTHONPATH test -d $PYTHONPATH || mkdir -p $PYTHONPATH ../visual-2.9.4/configure --prefix=/opt/python make make install Somewhere, the setting of prefix is getting lost. My /opt/python/bin/vpython script starts like this: #!/bin/sh # Variables determined by configure. PYTHON=/usr/bin/python2.2 visualdemodir=${prefix}/lib/python2.2/site-packages/visual/demos visualidledir=/opt/python/lib/python2.2/site-packages/visual/idle_VPython IDLE=idle.py Note that visualdemodir depends on ${prefix}, but prefix isn't defined anywhere. Further, I would think that my needed setting of PYTHONPATH should be included in the vpython script. Finally, note that the setting of PYTHON in the vpython script is pointless since it isn't exported. My final fixed vpython script starts like this: #! /bin/sh # Variables determined by configure. PYTHON=/usr/bin/python2.2 PYTHONPATH=/opt/python/lib/python2.2/site-packages export PYTHON PYTHONPATH prefix=/opt/python visualdemodir=${prefix}/lib/python2.2/site-packages/visual/demos visualidledir=/opt/python/lib/python2.2/site-packages/visual/idle_VPython IDLE=idle.py but tracing the code paths through configure, I see that visualdemodir and visualidledir are (at least superficially) treated quite differently, so I'm not sure of the best way to patch things up. Next, I'll try running it on various applications I have. -- Andy Dougherty dou...@la... Dept. of Physics Lafayette College, Easton PA 18042 |