forked from OSchip/llvm-project
[lldb/Docs] Update the Windows documentation
Update the build instructions for Windows with my recent experience.
This commit is contained in:
parent
80c3ea4e63
commit
ae73891164
|
@ -34,7 +34,7 @@ If you want to run the test suite, you'll need to build LLDB with Python
|
||||||
scripting support.
|
scripting support.
|
||||||
|
|
||||||
* `Python <http://www.python.org/>`_
|
* `Python <http://www.python.org/>`_
|
||||||
* `SWIG <http://swig.org/>`_
|
* `SWIG <http://swig.org/>`_ 2 or later.
|
||||||
|
|
||||||
Optional Dependencies
|
Optional Dependencies
|
||||||
*********************
|
*********************
|
||||||
|
@ -79,29 +79,38 @@ commands below.
|
||||||
Windows
|
Windows
|
||||||
*******
|
*******
|
||||||
|
|
||||||
* Visual Studio 2015 or greater
|
* Visual Studio 2017.
|
||||||
* Windows SDK 8.0 or higher. In general it is best to use the latest available
|
* The latest Windows SDK.
|
||||||
version.
|
* The Active Template Library (ATL).
|
||||||
* `GnuWin32 <http://gnuwin32.sourceforge.net/>`_
|
* `GnuWin32 <http://gnuwin32.sourceforge.net/>`_ for CoreUtils and Make.
|
||||||
* `Python 3.5 or higher <https://www.python.org/downloads/windows/>`_ or
|
* `Python 3.6 <https://www.python.org/downloads/windows/>`_. Python 3.7 is
|
||||||
higher. Earlier versions of Python can be made to work by compiling your own
|
known to be incompatible. More recent versions might work but are untested.
|
||||||
distribution from source, but this workflow is unsupported and you are own
|
Make sure to get the x64 variant if that's what you're targetting and install
|
||||||
your own.
|
the debug library if you want to build in debug.
|
||||||
* `Python Tools for Visual Studio
|
* `Python Tools for Visual Studio
|
||||||
<https://github.com/Microsoft/PTVS/releases>`_. If you plan to debug test
|
<https://github.com/Microsoft/PTVS/releases>`_. If you plan to debug test
|
||||||
failures or even write new tests at all, PTVS is an indispensable debugging
|
failures or even write new tests at all, PTVS is an indispensable debugging
|
||||||
extension to VS that enables full editing and debugging support for Python
|
extension to VS that enables full editing and debugging support for Python
|
||||||
(including mixed native/managed debugging)
|
(including mixed native/managed debugging).
|
||||||
|
|
||||||
The steps outlined here describes how to set up your system and install the
|
The steps outlined here describes how to set up your system and install the
|
||||||
required dependencies such that they can be found when needed during the build
|
required dependencies such that they can be found when needed during the build
|
||||||
process. They only need to be performed once.
|
process. They only need to be performed once.
|
||||||
|
|
||||||
#. Install Visual Studio and the Windows SDK.
|
#. Install Visual Studio with the Windows SDK and ATL components.
|
||||||
#. Install GnuWin32, making sure ``<GnuWin32 install dir>\bin`` is added to
|
#. Install GnuWin32, making sure ``<GnuWin32 install dir>\bin`` is added to
|
||||||
your PATH environment variable.
|
your PATH environment variable. Verify that utilities like ``dirname`` and
|
||||||
|
``make`` are available from your terminal.
|
||||||
#. Install SWIG for Windows, making sure ``<SWIG install dir>`` is added to
|
#. Install SWIG for Windows, making sure ``<SWIG install dir>`` is added to
|
||||||
your PATH environment variable.
|
your PATH environment variable. Verify that ``swig`` is available from your
|
||||||
|
terminal.
|
||||||
|
#. Register the Debug Interface Access DLLs with the Registry from a privileged
|
||||||
|
terminal.
|
||||||
|
|
||||||
|
::
|
||||||
|
|
||||||
|
> regsvr32 "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\DIA SDK\bin\msdia140.dll"
|
||||||
|
> regsvr32 "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\DIA SDK\bin\amd64\msdia140.dll"
|
||||||
|
|
||||||
Any command prompt from which you build LLDB should have a valid Visual Studio
|
Any command prompt from which you build LLDB should have a valid Visual Studio
|
||||||
environment setup. This means you should run ``vcvarsall.bat`` or open an
|
environment setup. This means you should run ``vcvarsall.bat`` or open an
|
||||||
|
|
Loading…
Reference in New Issue