# HG changeset patch
# User Merlijn van Deen <valhallasw@gmail.com>
# Date 1337635677 -7200
# Node ID ea634a8770fe83bae22401007d22edb182be09e5
# Parent  2802b03060b2234ee9c20bdbc6f8181a45c9ffaf
Windows devguide: most build errors are due to missing optional dependencies

Added notes to the "Quickstart" and "Getting Set Up" section to clarify the
build errors that occur when not all optional dependencies are met.

diff -r 2802b03060b2 -r ea634a8770fe index.rst
--- a/index.rst	Mon May 21 20:31:44 2012 +0200
+++ b/index.rst	Mon May 21 23:27:57 2012 +0200
@@ -45,7 +45,9 @@
 
    On :ref:`Windows <windows-compiling>`, load the project file
    :file:`PCbuild\\pcbuild.sln` in Visual Studio, select :menuselection:`Debug`,
-   and :menuselection:`Build --> Build Solution`.
+   and :menuselection:`Build --> Build Solution`. If you have not installed the
+   dependencies for all subpackages, you will get several missing file errors.
+   You can ignore them if you are not working on those packages.
 3. :doc:`Run the tests <runtests>` with ``./python -m test -j3`` (use
    :file:`./python.exe` on :ref:`most <python.exe>` Mac OS X systems and
    :file:`PCbuild\\python_d.exe` on Windows; replace ``test`` with
diff -r 2802b03060b2 -r ea634a8770fe setup.rst
--- a/setup.rst	Mon May 21 20:31:44 2012 +0200
+++ b/setup.rst	Mon May 21 23:27:57 2012 +0200
@@ -74,6 +74,7 @@
 only on pure Python code the pydebug build provides several useful checks that
 one should not skip.
 
+.. _build_dependencies:
 
 Build dependencies
 ''''''''''''''''''
@@ -175,6 +176,11 @@
 associated with the F7 key. Make sure you have chosen the "Debug" option from
 the build configuration drop-down first.
 
+During the compilation, you might get several errors in projects that need
+external dependencies, such as *_bz2* and *_hashlib*. You can ignore these if
+you are not working on those projects - the *python* package will still produce
+a working interpreter - see also :ref:`build_dependencies`. 
+
 Once built you might want to set Python as a startup project. Pressing F5 in
 Visual Studio, or choosing Start Debugging from the Debug menu, will launch
 the interpreter.