https://bugs.kde.org/show_bug.cgi?id=407200

--- Comment #3 from Alexander Semke <alexander.se...@web.de> ---
(In reply to avlas from comment #2)
> (In reply to Alexander Semke from comment #1)
> > The only way to achieve this at the moment is to recompile Cantor with
> > python headers and libs from the conda environment. So, cantor has to be
> > linked against this environment...
> 
> It would be great if this could be easily modified from settings (as it can
> be done for other backends). I thought that just replacing which python is
> used could be enough, but I guess I was too optimistic.
For other backends like Maxima for example we communicate with the executable
via stdin/stdout. For this the user have to or can specify the path for the
executable. For scripting languages like python and julia we embedd the
interpreter into our process at runtime. Which interpreter to use is determined
during the compilation and linking to the python libraries.


> This is a workaround I could use as I'm actually compiling Cantor myself
> because of bug https://bugs.kde.org/show_bug.cgi?id=406712
I'll check this bug report.


> Could you please let me know how to build linking to Conda instead? I tried
> compiling Cantor from scratch inside Conda's environment but this is
> creating lots of cmake errors because of things that are not python related.
I'm not familiar with Conda but this "environment" also has to store the files
somewhere. I think what you're looking for can achieved if you manage cmake to
find the python installation from this environment. Please have a look at
cmake/FindPythonLibs3.cmake. The variables PYTHONLIBS3_LIBRARIES and
PYTHONLIBS3_INCLUDE_DIRS are used at compile and linking time and determine the
python environment to use. This cmake script is looking for Python.h and for
python3.2m. You can provide hints here by setting the environment variables
PYTHONLIBS3_INCLUDEDIR and PYTHONLIBS3_LIBDIR in your shell. Just point these
variables to your conda installation and it should work.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to