forked boostpythongenerator project to separate the generatorrunner

so that it could be used independently; the qtdoc generator module
remained part of generatorrunner

2 files changed, 10 insertions, 9 deletions

diff --git a/doc/compiling/cmake-primer.rst b/doc/compiling/cmake-primer.rst
index 7769005be..499b8433a 100644
--- a/doc/compiling/cmake-primer.rst
+++ b/doc/compiling/cmake-primer.rst
@@ -6,7 +6,7 @@ CMake primer
 ************
 
 This chapter is a basic introduction to CMake, the build system used by PySide
-and the boost binding generator.
+and the binding generator runner.
 
 The practical steps will focus on how to use cmake on a Unix-like (GNU/Linux)
 environment.
diff --git a/doc/compiling/setup-generator.rst b/doc/compiling/setup-generator.rst
index d58f98368..2118a352c 100644
--- a/doc/compiling/setup-generator.rst
+++ b/doc/compiling/setup-generator.rst
@@ -1,17 +1,18 @@
 
-.. _boost-python-generator:
+.. _generatorrunner:
 
-***********************
-Boost::Python Generator
-***********************
+****************
+Generator Runner
+****************
 
 Overview
 =========================================
 
-The **Boost::Python Generator** (A.K.A. :program:`boostpythongenerator`) is
-the program that creates the bindings source files from Qt headers and
-auxiliary files  (typesystems, ``global.h`` and glue files). It makes
-heavy use of the :ref:`api-extractor` library.
+The **GeneratorRunner** (A.K.A. :program:`generatorrunner`) is
+the program that collects relevant data from C++ headers (paying
+special attention to Qt provided information, like signals and
+properties) and auxiliary files (typesystems, ``global.h`` and
+glue files). For this it relies on the :ref:`api-extractor` library.
 
 
 Getting the sources