Use a different cross-compile prefix for 64-bit Windows

[builder.git] / Readme.txt

diff --git a/Readme.txt b/Readme.txt
index 9ae07f62c1ce4e191950218a550c617675ef3e11..16def7c04c0f1062ac0892cd3085fc5c5d2fbb57 100644 (file)
--- a/Readme.txt
+++ b/Readme.txt
@@ -34,11 +34,10 @@ builds, cross-compilation and pkg-config integration.
 
 2. Building Builder
 
-Builder is normally built using itself.  However, if you just downloaded the
-source and don't yet have a Builder binary, how is that possible?  To resolve
-this problem, there's a script called bootstrap.sh in the Builder main
-directory.  Before running it, make sure you have the following libraries
-available:
+Builder is normally built using itself.  This creates a conundrum if you just
+downloaded the source and don't yet have a Builder binary.  To resolve the
+problem, there's a script called bootstrap.sh in the Builder main directory.
+Before running it, make sure you have the following libraries available:
 
 MSP libraries: core datafile
 
@@ -47,10 +46,9 @@ Others: sigc++-2.0
 You should be able to get the MSP libraries from the same place you got
 Builder itself from.  Since they are also normally built with Builder, the
 script will need to have their sources available.  By default, it will look at
-the parent directory of builder.  You can change this by setting the LIBPATH
-evironment variable for the script.  If everything goes well, the script will
-build a builder-stage1 binary and then proceed to build a normal version with
-it.
+the parent directory of builder.  You can change this with the --libpath
+parameter for the script.  If everything goes well, the script will build a
+builder-stage1 binary and then proceed to build a normal version with it.
 
 -------------------------------------------------------------------------------
 
@@ -435,9 +433,9 @@ library components from the same package:
 
   use "mylib_common";
 
-Libraries used in this way will always be linked in statically.  This can be
-useful in organizing code when multiple components in a package share a common
-part.
+This can be useful in organizing code when multiple components in a package
+share a common part.  If the used library is not specified to be installed,
+it will be linked statically.  
 
 Packages may want to offer optional features, for example to allow the user to
 choose whether to use a particular external library:
@@ -460,8 +458,8 @@ conditional statement may be used:
   };
 
 Any statements inside the conditional block are evaluated if the feature is
-enabled.  This can be negated with a !.  Conditionals can appear at the package
-level and may contain anything that the package statement can.
+enabled.  This can be negated with a !.  Conditionals can appear at package and
+component scopes and may contain anything that the enclosing statement can.
 
 When making cross-platform software, it's often necessary to use different
 libraries on different platforms.  Another kind of conditional can be used for