<font color='black' size='2' face='arial'>If I wer<font size="2">e going to analyze this problem (and I'm not, that<font size="2">'s why I'm telling you how I would if I were going to.....) then I would:<br>
<br>
<font size="2">- gat<font size="2">her up all the matches of "[Pp]ython" <font size="2">from the CMa<font size="2">keCache.txt file</font></font></font></font><br>
<font size="2">- compare/contrast that with your ini<font size="2">tial explicitly specified cache <font size="2">variables<br>
<font size="2">- look in the FindPy<font size="2">*</font> modules (VTK, built into CMake, custom?)</font> to see what variab<font size="2">les are a<font size="2">ctually used for VTK-wrapped p<font size="2">ython, and then...<br>
<font size="2"><br>
- </font>specif<font size="2">y the set of variables needed by those find modules to come up with the right cache contents<br>
<br>
<br>
<font size="2">Unfortun<font size="2">ately, the python stu<font size="2">ff is still a bit m<font size="2">essy. There's no way to get a consistent set of stuff just by setting a single vari<font size="2">able like you can with Qt and QT_<font size="2">QMAKE_EXECUTABLE.<br>
<br>
</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font><font size="2" color="black" face="arial">
<div> <br>
</div>
<div> <br>
</div>
<div> <br>
</div>
<div style="font-family:arial,helvetica;font-size:10pt;color:black">-----Original Message-----<br>
From: Sean McBride <sean@rogue-research.com><br>
To: David Gobbi <david.gobbi@gmail.com><br>
Cc: David Cole <dlrdave@aol.com>; vtk-developers <vtk-developers@vtk.org><br>
Sent: Mon, Feb 11, 2013 3:42 pm<br>
Subject: Re: [vtk-developers] ppc-debug dashboard link error<br>
<br>
<div id="AOLMsgPart_0_f172727d-10b9-4e8b-9ba4-7a7243163f9b" style="margin: 0px;font-family: Tahoma, Verdana, Arial, Sans-Serif;font-size: 12px;color: #000;background-color: #fff;">
<pre style="font-size: 9pt;"><tt>On Mon, 11 Feb 2013 09:42:56 -0700, David Gobbi said:
>No need for a verbose build, the configure summary that it dumps to
>the dashboard is enough. It reports this:
>
> Found PythonLibs: /usr/lib/libpython2.5.dylib
>
>even though PYTHON_LIBRARY was set to this:
>
> /Library/Frameworks/Python.framework/Versions/2.7/lib/libpython2.7.dylib
>
>Maybe your python install also created a libpython2.7.a that you can try
>instead? Or maybe it also put the libraries in /usr/local/lib?
So today I set:
SET (PYTHON_EXECUTABLE "/System/Library/Frameworks/Python.framework/Versions/2.5/bin/python")
SET (PYTHON_LIBRARY "/System/Library/Frameworks/Python.framework/Versions/2.5/Python")
SET (PYTHON_INCLUDE_DIR "/System/Library/Frameworks/Python.framework/Versions/2.5/Headers")
and I'm sure they exist:
$ /System/Library/Frameworks/Python.framework/Versions/2.5/bin/python --version
Python 2.5.1
$ file /System/Library/Frameworks/Python.framework/Versions/2.5/Python
/System/Library/Frameworks/Python.framework/Versions/2.5/Python: Mach-O
universal binary with 4 architectures
$ ls /System/Library/Frameworks/Python.framework/Versions/2.5/Headers
Python-ast.h cStringIO.h complexobject.h floatobject.h intrcheck.h
etc...
oddly, it still shows:
-- Found PythonLibs: /usr/lib/libpython2.5.dylib
but at least that's a symlink to the file I specified... still, odd that it's
not using the exact path I specified. Looking in the CMakeCache.txt I see that
it's also not using the correct executable at all:
PYTHON_EXECUTABLE:FILEPATH=/usr/local/bin/python
That's a 2.6 version... probably explains the link error... but why is it
ignoring the explicit python choices???
Anyway, it's now building yet again after I deleted a bunch of old symlinks,
cleaned up $PATH, etc.
Cheers,
--
____________________________________________________________
Sean McBride, B. Eng <a href="mailto:sean@rogue-research.com">sean@rogue-research.com</a>
Rogue Research <a href="http://www.rogue-research.com" target="_blank">www.rogue-research.com</a>
Mac Software Developer Montréal, Québec, Canada
</tt></pre>
</div>
<!-- end of AOLMsgPart_0_f172727d-10b9-4e8b-9ba4-7a7243163f9b -->
</div>
</font></font>