diff options
| author | Ross Burton <ross.burton@arm.com> | 2025-11-04 19:26:02 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-11-04 11:26:02 -0800 |
| commit | 0ae0ac0f004d4028051ba01335b02ebadd2b8b4d (patch) | |
| tree | ff0632c7b2791eedb94df3903feaa43034ef55b7 /llvm/lib/Target/WebAssembly/WebAssemblyFixFunctionBitcasts.cpp | |
| parent | 5be12e1c95e897a9da713d49255868eea7ad60fa (diff) | |
| download | llvm-0ae0ac0f004d4028051ba01335b02ebadd2b8b4d.zip llvm-0ae0ac0f004d4028051ba01335b02ebadd2b8b4d.tar.gz llvm-0ae0ac0f004d4028051ba01335b02ebadd2b8b4d.tar.bz2 | |
[cmake] Pass PYTHON_EXECUTABLE to native builds (#163574)
Ensure that the nested native build uses the same python interpreter as
the main build, in case the python that CMake detects first is not the
python that the user has specified explicitly.
For example, if the person building LLVM wants to use a different python
interpreter to build (eg, testing the build with `python3.14` when
`python3` is a link to `python3.8`, or the default python doesn't have
development headers available) then they could add
`-DPYTHON_EXECUTABLE=python3.14` when invoking CMake. This should be
forwarded to the native CMake build to ensure that the same python is
used.
Original fix by Anuj Mittal <anuj.mittal@intel.com>.
Diffstat (limited to 'llvm/lib/Target/WebAssembly/WebAssemblyFixFunctionBitcasts.cpp')
0 files changed, 0 insertions, 0 deletions