Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

I'm about 90% of the way there on the native code side. The last part is tricky, but still mechanical. After I finish that the trick is going to be getting the test suite running. I suspect that will be nasty, just because there's a few thousand lines of code and it's going to be a pain to find

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

I'll work my way backwards . Eventually I'll get there. Anyway if you need any help on adding python 3 support , I'll be more than happy to help thanks , Que On 07/10/15 20:40, Zachary Turner wrote: When you built LLDB, did you specify a -DPYTHON_HOME= on your CMake command line, and also run

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

When you built LLDB, did you specify a -DPYTHON_HOME= on your CMake command line, and also run the install_custom_python.py script? There's a lot of steps, so it seems like almost everybody misses at least one step when doing this. I'm actively working (as in, literally right now) on getting LLDB

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

Hi Zachary, Ok so I did end up reconfiguring it and rebuilding but that was no help . I then realized that I was importing python27.dll as well as python27_d.dll . When I rebuilt liblldb I started getting an single unresolved error for imp_Py_InitModule which I guess was the symbol for the Py_

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

A couple of fixes to the Python/LLDB Windows build process were committed on Oct 1st, I suggest you try building a more recent revision (especially if setting CMAKE_BUILD_TYPE to Debug as suggested by Zach fixes your issue). On 6/10/2015 3:15 AM, Zachary Turner via lldb-dev wrote: Are you usi

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

Ok , I'll do that and get back to you . cheers, Que On 05/10/15 21:21, Zachary Turner wrote: Can you try to regenerate CMake with that command line and see if that helps? On Mon, Oct 5, 2015 at 1:17 PM kwadwo amankwa > wrote: No On 05/10/15 21:15, Zacha

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

Can you try to regenerate CMake with that command line and see if that helps? On Mon, Oct 5, 2015 at 1:17 PM kwadwo amankwa wrote: > > No > > On 05/10/15 21:15, Zachary Turner wrote: > > Are you using -DCMAKE_BUILD_TYPE=Debug when you generate CMake? > > On Mon, Oct 5, 2015 at 1:14 PM kwadwo ama

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

No On 05/10/15 21:15, Zachary Turner wrote: Are you using -DCMAKE_BUILD_TYPE=Debug when you generate CMake? On Mon, Oct 5, 2015 at 1:14 PM kwadwo amankwa > wrote: Thanks for the response , sorry for the delay. As a matter of fact I actually got rid of the

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

Are you using -DCMAKE_BUILD_TYPE=Debug when you generate CMake? On Mon, Oct 5, 2015 at 1:14 PM kwadwo amankwa wrote: > Thanks for the response , sorry for the delay. As a matter of fact I > actually got rid of the system python and installed my custom version. I > do suspect it is a linking pr

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

Thanks for the response , sorry for the delay. As a matter of fact I actually got rid of the system python and installed my custom version. I do suspect it is a linking problem though. When I build liblldb.dll it always loads python27.dll instead of python27_d.dll. Do you happen to know where

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

October 05, 2015 10:57 AM *To:* kwadwo amankwa; lldb-dev@lists.llvm.org *Subject:* Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows Are you using MSBuild or Ninja to build (i.e. are you clicking the Build Solution button in Visual Studio or running ninja fro

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

...@lists.llvm.org] On Behalf Of Zachary Turner via lldb-dev Sent: Monday, October 05, 2015 10:57 AM To: kwadwo amankwa; lldb-dev@lists.llvm.org Subject: Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows Are you using MSBuild or Ninja to build (i.e. are you cl

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

Are you using MSBuild or Ninja to build (i.e. are you clicking the Build Solution button in Visual Studio or running ninja from command line)? I don't know where it puts this stuff with a VS2013 build, but with a ninja build, your directory will be organized like this: build |___bin |___lldb

[lldb-dev] " Import error: No module named embedded_interpreter" on windows

Hi guys, Can someone point me in the right direction on this . I have managed to set up my environment on windows , compiling python2.7.10 using VS2013 and building llvm/lldb in VS2013. lldb and all its libraries build successfully so its just when I import lldb into my python project I get t