Put output files for foreign archs in their own directories

[builder.git] / Readme.txt

diff --git a/Readme.txt b/Readme.txt
index c0004ad9ad4f866fd350acb8c860a4ab0059a1ab..8c5ed2498d4b648639b015003445540c913c4eaf 100644 (file)
--- a/Readme.txt
+++ b/Readme.txt
@@ -16,12 +16,26 @@ 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:
 
-MSP libraries: misc core parser path regex++ getopt++
+MSP libraries: core datafile path strings io
 
 Others: sigc++-2.0
 
 Since the MSP libraries are also normally built with Builder, the script will
-need to have their sources available.  By default, it will look at ../libs.
-You can change this by setting the LIBPATH evironment variable for the script.
-If everything goes well, you should have a builder-stage1 binary that you can
-use to build a normal version of Builder.
+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, you should have a
+builder-stage1 binary that you can use to build a normal version of Builder.
+
+
+* Using Builder in your project
+
+To use Builder, you need to create a Build file that tells what it should
+build.  This file defines two main types of entities: packages and components.
+usually there is only one package definition in a Build file.
+
+The Build file uses a C-like structured language.  It consists of statements
+and blocks.  Statements are terminated with a semicolon (';').  Blocks are
+enclosed in braces ('{' and '}').  If a statement contains a block of
+substatements, the semicolon comes after the closing brace.
+
+For a simple example, look at Builder's own Build file.