[Lldb-commits] [PATCH] D17521: Update website for building and testing on Windows

Petr Hons via lldb-commits lldb-commits at lists.llvm.org
Mon Feb 22 15:44:01 PST 2016

Honsik added a comment.

Hello, newcomer here.

Thanks zturner for you support.
Shouldn't best workflow for VS also be mentioned? Like one solution for code editing generated by CMake -G "Visual Studio 14" that lacks directory structure (mostly CMake + VS issue) and another with custom project containg test case in llvm/tools/lldb/packages directory for creating test cases and running them with setting zturner has posted?

I am currently using different approach, editing code in Eclipse (it follows directory structure) and using VS only for debugging.

Or documentation shouldn't contain these recommendations?

Comment at: www/test.html:57
@@ -52,3 +56,3 @@
               <br />> cd $lldb/test
-              <br />> python dotest.py --executable <path-to-lldb>  -p TestInferiorCrashing.py
+              <br />> python dotest.py --executable <path-to-lldb>  -p TestInferiorCrashing.py ../packages/Python/lldbsuite/test
Hi, I have currently problem with running python dotest.py here.
When I have Debug build, it just fails to find _lldb module to import:

Traceback (most recent call last):
  File "d:\workspace\build\ninja\lib\site-packages\lldb\__init__.py", line 43, in swig_import_helper
    fp, pathname, description = imp.find_module('_lldb', [dirname(__file__)])
  File "d:\workspace\python\lib\imp.py", line 296, in find_module
    raise ImportError(_ERR_MSG.format(name), name=name)
ImportError: No module named '_lldb'

So i had to use python_d and then its working correctly


More information about the lldb-commits mailing list