[LLDB][Windows] Fix bundled Python 3.10.2 for branch "2023_0630_llvm15_release" · Pull Request !265 · OpenHarmony/third_party_llvm-project

### Issue

https://gitee.com/openharmony/third_party_llvm-project/issues/I7JMZ6

## Reason (Purpose, Solved Problem)

As for Windows, Python 3.10.2 used by LLDB is broken:

1. It lacks several built-in modules (e.g. `_struct`) so that LLDB does not initialie its Python interpreter correctly. A prompt shows when launching `lldb.exe`:

```
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "D:\XXX\lldb\__init__.py", line 105, in <module>
    import six
  File "D:\XXX\six.py", line 644, in <module>
    import struct
  File "D:\XXX\struct.py", line 13, in <module>
    from _struct import *
ModuleNotFoundError: No module named '_struct'
```

2. An error occurs if we want to run Python code in LLDB:

```
(lldb) script print("Hello world!")
Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name 'run_one_line' is not defined
Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name 'run_one_line' is not defined
Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name 'run_one_line' is not defined
Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name 'run_one_line' is not defined
Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name 'run_one_line' is not defined
Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name 'run_one_line' is not defined
Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name 'run_python_interpreter' is not defined
Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name 'lldb' is not defined
```

## Description

One way to fix this issue is building Python with LLVM other than using the prebuilt one:

1. Add `llvm-build/python_builder.py` which Python can be built with.

2. Add `--build-python` to `llvm-build/build.py`. If this option is specified, Python is built before building LLVM for Windows. In this case, the prebuilt Python is not used. This option is added in case `autoreconf` required for building Python is not installed on building machines.

3. Prebuilt Python is used by default (if `--build-python` is not present).

### How to build

With this PR, building on Linux fails unless `llvm` and `MinGW-w64` are built first. The script for building is provided by [\[LLDB\]\[Windows\] Fix bundled Python 3.10.2](https://gitee.com/openharmony/third_party_llvm-project/pulls/264).

The steps of building are outlined as follows:

1. Fetch [LLVM's PR](https://gitee.com/openharmony/third_party_llvm-project/pulls/264)

```
cd $HOME/llvm-toolchain/toolchain/llvm-project
git fetch https://gitee.com/openharmony/third_party_llvm-project.git pull/264/head:pr_264 && git cherry-pick pr_264
```

2. Build LLVM

```
cd $HOME/llvm-toolchain
# update prebuilts, no need to run each time
./toolchain/llvm-project/llvm-build/env_prepare.sh
# build
python3 ./toolchain/llvm-project/llvm-build/build.py
```

## Test (Local test)

1. Using prebuilt Python, compilation with `python3 toolchain/llvm-project/llvm-build/build.py` succeded.
 
2. Compilation with Python built first and used as a dependency of LLVM (`python3 toolchain/llvm-project/llvm-build/build.py --build-python`) passed.

### Need to cherry-pick to release (eg：monthly_20221018, OpenHarmony-3.2-Beta5 ...) branch？

- [ ] yes，branch list:
- [x] no

why:

类型	指派人员	状态
审查	hhj 已审查通过 Pavel Kosov	已完成 (1/1人)
测试	openharmony_ci 已测试通过 hhj 已测试通过	已完成 (2/1人)

OpenHarmony/third_party_llvm-project .gitee-modal { width: 500px !important; }

搜索帮助

OpenHarmony/third_party_llvm-project