From 04c528138b4ebe96ce84786a74c29e48d63f1c12 Mon Sep 17 00:00:00 2001
From: Dave Abrahams <dave@boostpro.com>
Date: Mon, 11 Dec 2006 05:22:04 +0000
Subject: [PATCH] Fully switch to BBv2

[SVN r36327]
---
 example/README            | 19 ++++++-------------
 example/tutorial/Jamrules | 36 ------------------------------------
 2 files changed, 6 insertions(+), 49 deletions(-)
 delete mode 100644 example/tutorial/Jamrules

diff --git a/example/README b/example/README
index a9bd7941..29a94f67 100644
--- a/example/README
+++ b/example/README
@@ -3,21 +3,14 @@
 .. file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
 
 To get started with the Boost Python Library, use the examples
-getting_started1.cpp and getting_started2.cpp.
+getting_started1.cpp and getting_started2.cpp.  Invoking
 
-    bjam -sTOOLS=your-toolset test
+    bjam --toolset=your-toolset test
 
-in this directory will build and run the examples.
-
-Other configuration variables may need to be set as described in
-http://www.boost.org/libs/python/doc/building.html.  These can be
-supplied by the environment, on the command-line with
-
-  -sVARIABLENAME=value
-
-or in the local Jamrules file.
+in this directory will build and run the examples.  See
+http://www.boost.org/more/getting_started.html for details about the
+--toolset= option.
 
 If you move this example from its place in the Boost development tree
-you'll need to edit at least one line in Jamrules and one line in
+you'll need to edit the two lines indicated in Jamroot and
 boost-build.jam.
-
diff --git a/example/tutorial/Jamrules b/example/tutorial/Jamrules
deleted file mode 100644
index dc50254a..00000000
--- a/example/tutorial/Jamrules
+++ /dev/null
@@ -1,36 +0,0 @@
-# Copyright David Abrahams 2003. See accompanying LICENSE for terms
-# and conditions of use.
-
-# If you move this example from its place in the Boost tree, edit this
-# path to point at the root directory of your Boost installation (the
-# one containing a subdirectory called "boost/" and a sub-subdirectory
-# "boost/python/" full of .hpp files).  Absolute paths work, too.
-#
-path-global BOOST_ROOT : ../../../.. ;
-
-# Boost.Python configuration variables, as described in
-# http://www.boost.org/libs/python/doc/building.html#configuration.
-# Usually you don't need to set these; the defaults will work.  If you
-# do set them, try to change as few of them as possible, starting with
-# the first ones.
-
-  # PYTHON_VERSION = <the two-part Major.Minor version number, e.g. 2.2> ;
-  # PYTHON_ROOT = <root directory of your Python installation, e.g. /usr> ;
-  # PYTHON_INCLUDES = <path to Python #include directories> ;
-  # PYTHON_LIB_PATH = <path to Python library object> ;
-
-# You may need to configure your compiler toolset, especially if you
-# want to build with a compiler that is not the "system default" or if
-# it is installed in a nonstandard place; see
-# http://www.boost.org/more/getting_started.html#Configuring for
-# details.  
-
-# Makes a project id for boost so that other Boost.Build projects can
-# refer to it by name.
-#
-project boost : $(BOOST_ROOT) ;
-
-# Change this setting to have all your built products placed under a
-# single directory:
-#
-# ALL_LOCATE_TARGET = <root directory for all built products>