zturner added a comment.
In http://reviews.llvm.org/D17521#359245, @Honsik wrote:
> 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?
Yea I can probably mention that.
================
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
</code>
----------------
Honsik wrote:
> 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
Good point, it has to be `python_d` on windows. I'll fix this note.
http://reviews.llvm.org/D17521
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
