Page MenuHomePhabricator

Update website for building and testing on Windows
ClosedPublic

Authored by zturner on Feb 22 2016, 2:29 PM.

Details

Reviewers
amccarth
Honsik
Summary

Lots of new info about how to build / test on Windows.

  1. Update for VS 2015 and Python 3.5
  2. Remove old info about building with Python 2.7
  3. Reformat the testing page to make it easier to read.
  4. Add info about installing and using PTVS on Windows.

Diff Detail

Event Timeline

zturner updated this revision to Diff 48734.Feb 22 2016, 2:29 PM
zturner retitled this revision from to Update website for building and testing on Windows.
zturner updated this object.
zturner added reviewers: amccarth, Honsik.
zturner added a subscriber: lldb-commits.
zturner updated this revision to Diff 48737.Feb 22 2016, 2:51 PM

Update to include full context.

amccarth edited edge metadata.Feb 22 2016, 3:12 PM

Could you post the patch with full context? It's easier to see the changes in context.

The information looks right. It's nice to see all the build-Python-yourself stuff simplified away.

www/build.html
63

typo: "on your own" not "own your own"

67

Wasn't there a particular version (like 3.0.5) that had a specific bug? I seem to recall you needed something older or something very recent.

www/test.html
67

delete "that"

139

Did you mean "managed" here? Would it be clearer to say you can step between the test script and the native LLDB code?

"Seamlessly" is a stretch. ;-)

160

It might be useful to give examples here. For one thing, it might not be obvious at this point that the Path and Windows Path fields should point do the _d version of the Python executable.

Honsik edited edge metadata.Feb 22 2016, 3:44 PM

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?

www/test.html
57

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

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.

www/test.html
57

Good point, it has to be python_d on windows. I'll fix this note.

zturner updated this revision to Diff 48751.Feb 22 2016, 4:06 PM
zturner edited edge metadata.

Updated with more info about using VS and ninja together, and a note about python_d on Windows.

Honsik accepted this revision.Feb 22 2016, 4:22 PM
Honsik edited edge metadata.
This revision is now accepted and ready to land.Feb 22 2016, 4:22 PM
Eugene.Zelenko added a subscriber: Eugene.Zelenko.

Committed in r261795.