This project is read-only.
Initial revised version based on the translation of Russian version

How to build PYKD

1. Taking the source

2. Set up the boost:: python
2.1 Download and install boost 1.40.0 from
2.2 Add environment variable BOOST_ROOT, set it to the location of your boost library's installation
for example: C: \ lib \ boost140_0
2.3 Building boost:: python
a. run bootstrap.bat in boost root to build bjam
b. In order to compile the appropriate libraries, run the following commands by setting the current directory to $ (BOOST_ROOT)
For x86:
bjam --stagedir=stage --with-python stage
And for x64:
bjam address-model=64 --stagedir=stage64 --with-python stage

In the setting of the project scored the following ways to build the library:
$ (BOOST_ROOT) \ stage - for x86 build
$ (BOOST_ROOT) \ stage64 - for x64 build

2.4 specific version of python
If you have several versions of python, and you want to explicitly specify the version of use, you must edit the user-config.jam and add a line, for example, are:
using python: 2.6;
using python: 2.7;
Now you can build libraries explicitly specify the version of python
For x86:
bjam --stagedir = stage --with-python stage python = 2.7
And for x64:
bjam address-model = 64 --stagedir = stage64 --with-python stage python = 2.7
You can read more:

If bjam can not build libs, try to set:
bjam --without-mpi stage

3. Setting up paths to python
To build the needed header files and library exports from the corresponding versions of python, environment variable PYTHONROOT is used to set pathon's installation location. If you have multiple versions of python installed, please make sure the python version you used to build boost:: python match the PYTHONROOT you set for pykd build.
For example, on my machine variable PYTHON_ROOT = C: \Python26. And the two versions (x86 and x64) python:
C: \ Python26 \ x86 \
C: \ Python26 \ x64 \

4. Double check pykd project setting (compile and link), make sure 'additional include directories' and 'additional library directories' point to the right location of header and libraries;

5. Setting up ways to DBG SDK
1. Install "debugging tools for windows";
2. Add an environment variable DBGSDKROOT to point to the SDK folder of windbg's installation.

Last edited Sep 16, 2011 at 1:02 PM by kernelnet, version 4


No comments yet.