msys2 / MINGW-packages

Package scripts for MinGW-w64 targets to build under MSYS2.
https://packages.msys2.org
BSD 3-Clause "New" or "Revised" License
2.25k stars 1.21k forks source link

Build LLDB with Python (Scripting) support #3222

Closed jhasse closed 4 years ago

jhasse commented 6 years ago

Required for https://github.com/vadimcn/vscode-lldb/issues/37 for example.

revelator commented 6 years ago

Unfortunatly it expects windows python and not mingw64 python, i been trying for some time to get it to accept the mingw64 python but so far no success. Needs a lot of hacking about in the cmake files i suspect.

Alexpux commented 6 years ago

I think FindPython module can be used from cmake or get it from one of the thousand projects. Our python is widely used when building with cmake

mewmew commented 6 years ago

@Alexpux do you know where to make the necessary changes? It would be great to see Python support in lldb enabled.

Cheers, /u

mewmew commented 6 years ago

@revelator With release 6.0, do you know if there is better support for Python that could help this issue?

revelator commented 6 years ago

Been bedwritten after major backsurgery so i havent had the time to look at it yet, but i suspect that it might still need windows python. Since the mingw64 python seems to be following the same layout as the posix version it might be possible to adjust the cmake files so that when the build chain detects MINGW* it will use this layout. Ill have a look at it soon.

Alexpux commented 6 years ago

I’m already do everything. Need just fix symbols visibility when building SWIG wrapper

mewmew commented 6 years ago

Been bedwritten after major backsurgery so i havent had the time to look at it yet

Hope you get better soon, and thanks for taking your time to give me insight into the current status of this issue.

revelator commented 6 years ago

Thanks, things are more or less back to normal, still getting a bit tired when up for more than a few hours but getting better by the day. Looks like Alex allready fixed up most of the problems like he mentioned above :), swig integration would be a nice next step.