From 09119398a441b231e0eae1ece7c649eeb1695aa0 Mon Sep 17 00:00:00 2001 From: Vladimir Prus Date: Tue, 2 Dec 2003 10:44:49 +0000 Subject: [PATCH] Tell to cd to Boost.Build root before running "bjam --version". Also link to site_config_targets. [SVN r21077] --- v2/boost_build_v2.html | 51 ++++++++++++++++++++++-------------------- 1 file changed, 27 insertions(+), 24 deletions(-) diff --git a/v2/boost_build_v2.html b/v2/boost_build_v2.html index 0b539ffca..27263c7ec 100644 --- a/v2/boost_build_v2.html +++ b/v2/boost_build_v2.html @@ -22,12 +22,12 @@ div.alert { color: red } table { align: center; border: thin; } - + + - build request, build request expansion and directly requested targets + - conditional properties + -->

Place the Boost.Jam binary, called "bjam" or "bjam.exe", somewhere in - your PATH. Verify that correct bjam is being executed by - running "bjam --version". You should get + your PATH. Go to the root directory of Boost.Build and run + "bjam --version". You should get 

       Boost.Build V2 (Milestone N)
      
@@ -208,12 +208,12 @@
       bjam there. A simple application will be built. You can also
       play with other projects in example. 
       
+                                                                                                                       it somewhere. 
+                                                                                                                        
+                                                                                                                          
It is slighly better way is to copy new/user-config.jam
+                                                                                                                          into one of the locations where it can be found (given in this table). This prevent you from
+                                                                                                                          accidentally overwriting your config when updating.
 -->
       
     
 
@@ -630,6 +630,9 @@ boost-build /path/to/boost.build ;
     Of course, you'll probably never in your life need debug version of zlib,
     but for other libraries this is quite reasonable. 
 
+    
More advanced use of prebuilt target is descibed in recipes.

+
     
Reference

     This section will document mostly high-level view of Boost.Build,
     mentioning appropriate modules and rules. The on-line help system must be
@@ -652,8 +655,8 @@ boost-build /path/to/boost.build ;
     language, and typically contains calls to functions provided by
     Boost.Build, which create main targets of needed type, declare project
     attributes and access other projects. The full list of functions provided
-    by Boost.Build is described below. Of course, user
-    can create his own functions, or it can directly access Boost.Build
+    by Boost.Build is described below. Of course,
+    user can create his own functions, or it can directly access Boost.Build
     internals from Jamfile, if builtin facilities are not sufficient.

 
     
Each main target, or project can be built in a number of ways, say
@@ -1058,17 +1061,17 @@ boost-build /path/to/boost.build ;
 
       
  • It allows to have main target names with slashes. 
       
+                                                                                    That makes good rationale for why main target must contain names.
+                                                                                     -->
       
    •