[clang] [clang] Only build clang-tblgen if it is actually needed (PR #161952)

2025-10-18 Thread Ross Burton via cfe-commits
rossburton wrote: So my approach was wrong. My goal is to not build clang-tblgen if it's already been provided, but not explode the build if it hasn't. Obviously I'm doing something wrong with this approach and either I need to fiddle the logic in `add_tablegen` or the behaviour I'm after alre

[clang] [clang-tools-extra] [compiler-rt] [libc] [libcxx] [lld] [lldb] [llvm] [mlir] [openmp] [polly] Python-related cleanups (PR #163566)

2025-10-18 Thread Ross Burton via cfe-commits
rossburton wrote: > Moreover, this may have pretty big implications since the implementation of > these commands 8s very inconsistent across platforms and no common rules seem > to exist. Some platforms have `python` that aliases to `python3`, some alias > it to `python2`, some only have `pyth

[clang] [clang] Support building native tools when cross-compiling standalone clang (PR #160605)

2025-10-18 Thread Ross Burton via cfe-commits
https://github.com/rossburton created https://github.com/llvm/llvm-project/pull/160605 When cross-compiling the LLVM project as a whole (from llvm/), if it cannot find presupplied tools it will create a native build environment to build the tools it needs. However, when doing a standalone bui

[clang] [clang-tools-extra] [compiler-rt] [libc] [libcxx] [lld] [lldb] [llvm] [mlir] [openmp] [polly] Python-related cleanups (PR #163566)

2025-10-18 Thread Ross Burton via cfe-commits
https://github.com/rossburton created https://github.com/llvm/llvm-project/pull/163566 Ensure that the nested native CMake build uses the same Python interpreter as the outer build. Unify python shebangs so that they use `python3` everywhere, instead of a mix of `python` and `python3`. >From

[clang] [clang-tools-extra] [compiler-rt] [libc] [libcxx] [lld] [lldb] [llvm] [mlir] [openmp] [polly] Python-related cleanups (PR #163566)

2025-10-18 Thread Ross Burton via cfe-commits
rossburton wrote: The PYTHON_EXECUTABLE and the shebang cleanups are entirely unrelated except by theme, I can split them it that would make things easier. https://github.com/llvm/llvm-project/pull/163566 ___ cfe-commits mailing list cfe-commits@lists

[clang] [clang] Only build clang-tblgen if it is actually needed (PR #161952)

2025-10-18 Thread Ross Burton via cfe-commits
rossburton wrote: Just marked as a draft as I'm thinking there _might_ be an case where you want to both use an existing tblgen _and_ build a new one: in complex multi-stage cross-compilation builds of clang. I'm not sure if this is overcomplicating things, or a realistic need. Either way, I

[clang] [clang-tools-extra] [compiler-rt] [libc] [libcxx] [lld] [lldb] [llvm] [mlir] [openmp] [polly] Python-related cleanups (PR #163566)

2025-10-17 Thread Ross Burton via cfe-commits
https://github.com/rossburton updated https://github.com/llvm/llvm-project/pull/163566 >From 19f755003adf1befe663543286950fb4ac3a Mon Sep 17 00:00:00 2001 From: Ross Burton Date: Wed, 15 Oct 2025 15:21:16 +0100 Subject: [PATCH 1/3] [cmake] Pass PYTHON_EXECUTABLE to native builds Ensure tha

[clang] [clang-tools-extra] [compiler-rt] [libc] [libcxx] [lld] [lldb] [llvm] [mlir] [openmp] [polly] Python-related cleanups (PR #163566)

2025-10-17 Thread Ross Burton via cfe-commits
rossburton wrote: The cmake/python/native commit has been split out to https://github.com/llvm/llvm-project/pull/163574. https://github.com/llvm/llvm-project/pull/163566 ___ cfe-commits mailing list [email protected] https://lists.llvm.org/cg

[clang] [clang] Only build clang-tblgen if it is actually needed (PR #161952)

2025-10-17 Thread Ross Burton via cfe-commits
rossburton wrote: And CI exploded, so I'll dig into that obviously. https://github.com/llvm/llvm-project/pull/161952 ___ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

[clang] [clang] Only build clang-tblgen if it is actually needed (PR #161952)

2025-10-17 Thread Ross Burton via cfe-commits
https://github.com/rossburton created https://github.com/llvm/llvm-project/pull/161952 It's possible to build clang with an existing clang-tblgen (common when cross-compiling, for instance) by setting CLANG_TABLEGEN_EXE. If this is the case there's no need to build it, as it won't be used. >