On 29/11/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
Andy, I made small changes to the Linux scripts that start our Python based samples to use the PYTHON_LIB environment variable, if it is defined, to find the Python library and interpreter. If you don't have the PYTHON_LIB variable defined the behavior is as before, the default Python interpreter on the path is used. I had to do that as my Linux desktop uses a Python older than 2.5 and switching to 2.5 breaks the whole desktop. Other Linux users may run into this as well so I thought it'd be nicer for the scripts to automatically point to the Python interpreter that's used to build as well. Could you please take a look? feel free to adjust/revert the change if it causes any issues... Thanks.
Just today hit this problem on the Mac! I just linked to the Python 2.5 in /usr/local which seems to be ok. Does your change mean you MUST specify PYTHON_LIB or does it just default to whichever you have installed? Cheers, -- Pete
