diff options
author | Martin Kelly <mkelly@xevo.com> | 2020-04-02 13:56:32 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2020-04-03 14:49:13 +0100 |
commit | a22200a646eaf42cd4902a2fe3358d29717ac129 (patch) | |
tree | 8940d58ef7464a555ac920efd6ff1a7ae63790b1 /meta/recipes-core/busybox | |
parent | 4b26eaf7152fb712aba47a0c746333578f58ee8d (diff) | |
download | openembedded-core-contrib-a22200a646eaf42cd4902a2fe3358d29717ac129.tar.gz |
cmake: fix Python executable with cmake
Currently, CMake has two ways of finding Python executables:
FindPythonInterp and FindPython/FindPython3. FindPythonInterp is
deprecated and may be removed at some point. Currently, python3native
sets PYTHON_EXECUTABLE, which FindPythonInterp uses. This is a problem
for a few reasons:
- Setting PYTHON_EXECUTABLE as an environment variable doesn't work, as
CMake needs it to be set as an explicit CMake option via -D.
- Projects using the newer FindPython/FindPython3 don't pickup the right
Python, as the newer routines use Python_EXECUTABLE and
Python3_EXECUTABLE.
Fix this by setting PYTHON_EXECUTABLE, Python_EXECUTABLE, and
Python3_EXECUTABLE using -D options to EXTRA_OECMAKE.
The CMake routines are documented below:
https://cmake.org/cmake/help/latest/module/FindPythonInterp.html
https://cmake.org/cmake/help/latest/module/FindPython.html
https://cmake.org/cmake/help/latest/module/FindPython3.html
Signed-off-by: Martin Kelly <mkelly@xevo.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-core/busybox')
0 files changed, 0 insertions, 0 deletions