$include_dir="/home/hyper-archives/boost-commit/include"; include("$include_dir/msg-header.inc") ?>
From: ghost_at_[hidden]
Date: 2007-09-07 17:34:28
Author: vladimir_prus
Date: 2007-09-07 17:34:27 EDT (Fri, 07 Sep 2007)
New Revision: 39160
URL: http://svn.boost.org/trac/boost/changeset/39160
Log:
Adjust faq entry about targets in site-config.jam
Text files modified: 
   trunk/tools/build/v2/doc/src/faq.xml |    12 +++++-------                            
   1 files changed, 5 insertions(+), 7 deletions(-)
Modified: trunk/tools/build/v2/doc/src/faq.xml
==============================================================================
--- trunk/tools/build/v2/doc/src/faq.xml	(original)
+++ trunk/tools/build/v2/doc/src/faq.xml	2007-09-07 17:34:27 EDT (Fri, 07 Sep 2007)
@@ -331,18 +331,16 @@
     <para>It is desirable to declare standard libraries available on a
       given system. Putting target declaration in Jamfile is not really
       good, since locations of the libraries can vary. The solution is
-      to put the following to site-config.jam.</para>    
+      to declare the targets in site-config.jam:</para>    
 <programlisting>
-import project ;
-project.initialize $(__name__) ;
 project site-config ;
 lib zlib : : <name>z ;
 </programlisting>
 
-    <para>The second line allows this module to act as project. The
-      third line gives id to this project — it really has no location
-      and cannot be used otherwise. The fourth line just declares a
-      target. Now, one can write:
+    <para>Recall that both <filename>site-config.jam</filename> and
+    <filename>user-config.jam</filename> are projects, and everything
+    you can do in a Jamfile you can do in those files. So, you declare
+    a project id and a target. Now, one can write:
 <programlisting>
 exe hello : hello.cpp /site-config//zlib ;
 </programlisting>