Is there documentation on how lldb\include\lldb\host\config.h is
generated? I'm again having the problem of the config trying to point to
the wrong Python installation.
When I run cmake, I explicitly point PYTHON_HOME to C:\Python36 like this:
cmake -GNinja -DLLVM_TEMPORARILY_ALLOW_OLD_TOOLCHAIN
Hey Adrian,
Config.h gets generated by expanding the corresponding CMake variables. If
you look at LLDBConfig.cmake, you can see that LLDB_PYTHON_HOME is computed
from PYTHON_EXECUTABLE. The problem appears that somehow CMake ignored your
specified PYTHON_HOME and decided to pick a different Pytho
Thanks for the info. Setting Python3_ROOT_DIR solves the problem.
Looking at the cmake output from before setting Python3_ROOT_DIR, cmake
looks for Python twice and finds it at the two different locations.
Early on:
-- Found PythonInterp: C:/Python36/python.exe (found version "3.6.8")
Which lo
On Thu, Feb 27, 2020 at 10:53 AM Adrian McCarthy
wrote:
> Thanks for the info. Setting Python3_ROOT_DIR solves the problem.
>
> Looking at the cmake output from before setting Python3_ROOT_DIR, cmake
> looks for Python twice and finds it at the two different locations.
>
> Early on:
>
> -- Found
So to make my previous explanation more concrete:
On Thu, Feb 27, 2020 at 11:05 AM Jonas Devlieghere
wrote:
>
>
> On Thu, Feb 27, 2020 at 10:53 AM Adrian McCarthy
> wrote:
>
>> Thanks for the info. Setting Python3_ROOT_DIR solves the problem.
>>
>> Looking at the cmake output from before setti
> This was all fixed in CMake 3.12.
For some definitions of "all fixed." ;-)
It seems weird to me that FindPython3 found the VS-distributed Python,
which isn't mentioned anywhere in the environment block, and that it chose
that one over the Python 3 installation that was in the path and that
inc
