On 29/11/2019 15:22, Kornel Benko wrote:
Am Fri, 29 Nov 2019 14:39:23 +0100
schrieb pdv <pdvissch...@edpnet.be>:
On 28/11/2019 13:36, Kornel Benko wrote:
Yes I see. At 2) one could drop the LYX_PYTHON_EXECUTABLE.
Are the LYX_ variables not supposed to be set by the developer/user?
Good point. LYX_ prefix is used only to distinguish with any other variables
used in e.g. underlying projects like 3rdparty ...
But one could see it differently.
Patrick
Kornel
My only concern is that there is no way then to select another python
version if there should be a problem with the latest installed one.
With macports one can install different versions and select an active
one. But cmake's FindPython3 seems not to honor that choice and returns
always the latest one installed.
I've tried to find out which version is actually used by LyX.
On MacOS LyX does not use the version found by CMake; At least not for
running the reconfigure script. This uses the python3 command which is
set by macports and which can be different from the one returned by
FindPython3.
Maybe there are other locations in lyx where another python is used?
Patrick
You will always have such problems. Create a package configured with python2.
Use this package on a different computer. The lyx-executable will use a python
found on this new computer.
The executables used on compile time (by make or cmake) may of course be
different from the executables used later by lyx.
FindPython3 is only responsive for python used at compile time.
Kornel
Seems obvious now. Thanks for clearing this up.
Patrick
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
