Thanks Luis. I’m trying to avoid system python, and to use the downloaded one.
Eric’s suggestion worked. Thanks though.
M
> On 29 Sep 2015, at 09:54, Luis J. Salvatierra wrote:
>
> Hi Matt,
>
> have you tried to build with the option 'MITK_USE_SYSTEM_PYTHON'
> enabled? If you enable this optio
>
> -Ursprüngliche Nachricht-
> Von: Clarkson, Matt [mailto:m.clark...@ucl.ac.uk]
> Gesendet: Dienstag, 29. September 2015 06:03
> An: MITK
> Betreff: [mitk-users] Weird Python console issue
>
> Hi All,
>
> we just upgraded to 2015.05.2 (yeah… thanks!). Ive been me
the paths in the PythonPath.h.in header should do the
trick for you.
Regards,
Eric
-Ursprüngliche Nachricht-
Von: Clarkson, Matt [mailto:m.clark...@ucl.ac.uk]
Gesendet: Dienstag, 29. September 2015 06:03
An: MITK
Betreff: [mitk-users] Weird Python console issue
Hi All,
we just upgraded
Hi Matt,
have you tried to build with the option 'MITK_USE_SYSTEM_PYTHON'
enabled? If you enable this option you'll have to set the
'PYTHON_EXECUTABLE' and 'PYTHON_INCLUDE_DIR' paths in the advance mode
(ccmake).
Regards,
Luis
On 29/09/15 06:03, Clarkson, Matt wrote:
> Hi All,
>
> we just upgra
Hi All,
we just upgraded to 2015.05.2 (yeah… thanks!). Ive been meaning to try the
python console for ages. But we have a different superbuild and folder
structure. So, I got our superbuild to build all the dependencies ZLIB, PCRE,
SWIG, Numpy, Python, SimpleITK, VTK with Python, CTK with Pytho